Permalink
Browse files

Site updated at 2012-05-16 04:30:28 UTC

  • Loading branch information...
1 parent b586eb8 commit 9048cf6fc26693e61b497fd9ec845ba8d311306f @zachlendon committed May 16, 2012
View
@@ -4,7 +4,7 @@
<title><![CDATA[Zach Lendon's Blog]]></title>
<link href="http://zachlendon.github.com/atom.xml" rel="self"/>
<link href="http://zachlendon.github.com/"/>
- <updated>2012-05-15T23:26:05-05:00</updated>
+ <updated>2012-05-15T23:30:26-05:00</updated>
<id>http://zachlendon.github.com/</id>
<author>
<name><![CDATA[Zach Lendon]]></name>
@@ -20,7 +20,7 @@
<id>http://zachlendon.github.com/blog/2012/05/15/improving-mobile-capabilities-of-geb-pages-and-spock-specifications</id>
<content type="html"><![CDATA[<p>I spoke this evening at <a href="ojug.org">OJUG</a> about automated testing of mobile web applicatios on mobile devices with <a href="http://www.gebish.org/">Geb</a> and <a href="http://code.google.com/p/spock/">Spock</a>. The source code that I demoed during the talk is on <a href="https://github.com/zachlendon/flashcards-grails/">GitHub</a>.</p>
-<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may be either not in the developer&#8217;s complete control and not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. For my forked version, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
+<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may not be in the developer&#8217;s complete control. And even when it is, it likely is not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. It&#8217;s just not an area that is refined to that level yet. For my forked &#8216;flashcards&#8217; app, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
<p>One challenge I referenced above is with the URL that you &#8216;drive&#8217; to using <a href="http://seleniumhq.org/docs/03_webdriver.html">WebDriver</a> is typically defined statically as a <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#url">url property in your Geb Page Object</a>. But what if you want to use the same page object but have a different url for your mobile version? And what if you want to define a different <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#at">at</a> condition when you have arrived at the page for mobile? Define mobileUrl and mobileAt properties of course - which I do in this base page class.</p>
@@ -94,7 +94,7 @@ <h1 class="entry-title">Improving Mobile Capabilities of Geb Pages and Spock Spe
<div class="entry-content"><p>I spoke this evening at <a href="ojug.org">OJUG</a> about automated testing of mobile web applicatios on mobile devices with <a href="http://www.gebish.org/">Geb</a> and <a href="http://code.google.com/p/spock/">Spock</a>. The source code that I demoed during the talk is on <a href="https://github.com/zachlendon/flashcards-grails/">GitHub</a>.</p>
-<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may be either not in the developer&#8217;s complete control and not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. For my forked version, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
+<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may not be in the developer&#8217;s complete control. And even when it is, it likely is not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. It&#8217;s just not an area that is refined to that level yet. For my forked &#8216;flashcards&#8217; app, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
<p>One challenge I referenced above is with the URL that you &#8216;drive&#8217; to using <a href="http://seleniumhq.org/docs/03_webdriver.html">WebDriver</a> is typically defined statically as a <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#url">url property in your Geb Page Object</a>. But what if you want to use the same page object but have a different url for your mobile version? And what if you want to define a different <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#at">at</a> condition when you have arrived at the page for mobile? Define mobileUrl and mobileAt properties of course - which I do in this base page class.</p>
View
@@ -97,7 +97,7 @@ <h1 class="entry-title"><a href="/blog/2012/05/15/improving-mobile-capabilities-
<div class="entry-content"><p>I spoke this evening at <a href="ojug.org">OJUG</a> about automated testing of mobile web applicatios on mobile devices with <a href="http://www.gebish.org/">Geb</a> and <a href="http://code.google.com/p/spock/">Spock</a>. The source code that I demoed during the talk is on <a href="https://github.com/zachlendon/flashcards-grails/">GitHub</a>.</p>
-<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may be either not in the developer&#8217;s complete control and not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. For my forked version, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
+<p>With the original forked application, different Sitemesh layouts were used for the mobile version (which leverages <a href="jquerymobile.com/">JQuery Mobile</a>) of the app vs. the non-mobile version. As can be found in many similar web applications, the mobile version acts as a slimmed down version of the desktop application, with limited functionality and different urls to access certain pages. This creates challenges when writing functional tests for the application - even with great frameworks such as Geb and Spock. While one way to address these challenges is to build the application differently so as to not encounter them, in reality that may not be in the developer&#8217;s complete control. And even when it is, it likely is not a viable solution for removing all &#8220;challenges&#8221; that will come about when trying to create functional tests around a mobile web application. It&#8217;s just not an area that is refined to that level yet. For my forked &#8216;flashcards&#8217; app, I addressed some of the challenges, but left many in place. With that as a baseline, I did, as part of my talk give a few examples of ways to address these challenges using Geb and Spock that I&#8217;d like to share.</p>
<p>One challenge I referenced above is with the URL that you &#8216;drive&#8217; to using <a href="http://seleniumhq.org/docs/03_webdriver.html">WebDriver</a> is typically defined statically as a <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#url">url property in your Geb Page Object</a>. But what if you want to use the same page object but have a different url for your mobile version? And what if you want to define a different <a href="http://www.gebish.org/manual/current/api/geb-core/geb/Page.html#at">at</a> condition when you have arrived at the page for mobile? Define mobileUrl and mobileAt properties of course - which I do in this base page class.</p>
View
@@ -14,14 +14,14 @@
<loc>
http://zachlendon.github.com/blog/2012/05/15/improving-mobile-capabilities-of-geb-pages-and-spock-specifications/
</loc>
- <lastmod>2012-05-15T23:24:44-05:00</lastmod>
+ <lastmod>2012-05-15T23:30:25-05:00</lastmod>
</url>
<url>
<loc>http://zachlendon.github.com/blog/archives/</loc>
- <lastmod>2012-05-15T23:24:44-05:00</lastmod>
+ <lastmod>2012-05-15T23:30:25-05:00</lastmod>
</url>
<url>
<loc>http://zachlendon.github.com/</loc>
- <lastmod>2012-05-15T23:24:44-05:00</lastmod>
+ <lastmod>2012-05-15T23:30:25-05:00</lastmod>
</url>
</urlset>

0 comments on commit 9048cf6

Please sign in to comment.