Testing Java Apps on Mobile Devices with Arquillian and Selenium
•
1 gefällt mir•12,370 views
Slides from my talk on Red Hat Developer Conference 2012 in Brno.
![Why Are We Doing This? ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Testing Java Apps on Mobile Devices with Arquillian and Selenium
Ähnlich wie Testing Java Apps on Mobile Devices with Arquillian and Selenium (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Testing Java Apps on Mobile Devices with Arquillian and Selenium
- 1. RichFaces – Testing on Mobile Devices Pavol Pitoňák Quality Assurance Engineer, Red Hat 17 Feb 2012
- 18. testng.xml
- 19. testng-ftest.xml
- 20. testng-all.xml
- 25. public void testIPad() {
- 27. }
- 28. }
- 30. @Deployment
- 31. public static JavaArchive createTestArchive() {
- 32. return ...;
- 33. }
- 34. @Test
- 37. }
- 38. }
- 39. Sample WebDriver Test public class SampleTest extends Arquillian { @Drone public WebDriver driver; @ArquillianResource private URL deployedRoot; @Deployment public static WebArchive createTestArchive() { return ...; } @Test public void testDefaultSkin() { driver.get(“http://devconf.cz”); ... } }
- 41. public static WebArchive createTestArchive() {
- 42. WebArchive war = ShrinkWrap.createFromZipFile(WebArchive.class, new File("target/richrates.war"));
- 43. }
- 44. ... or construct the WAR yourself :)
- 46. public static WebArchive createTestArchive() {
- 47. WebArchive war = ShrinkWrap.createFromZipFile(WebArchive.class, new File("target/richrates.war"));
- 48. }
- 49. ... or construct the WAR yourself :)
- 51. public static WebArchive createTestArchive() {
- 52. MavenDependencyResolver resolver = DependencyResolvers.use(MavenDependencyResolver.class).loadMetadataFromPom( "pom.xml");
- 53. WebArchive war = ShrinkWrap.create(WebArchive.class, "richrates.war");
- 63. return war;
- 64. }
- 66. <property name="implementationClass"> org.openqa.selenium.firefox.FirefoxDriver </property>
- 67. </extension>
- 70. Maven profiles
- 71. Sample WebDriver Test public class SampleTest extends Arquillian { @Drone public WebDriver driver; @ArquillianResource private URL deployedRoot; @Deployment public static WebArchive createTestArchive() { return ...; } @Test public void testDefaultSkin() { driver.get(“http://devconf.cz”); ... } }
- 74. WebDriver driver = ...
- 76. GoogleSearchPage page = PageFactory.initElements(driver,GoogleSearchPage.class);
- 78. }
- 83. @FindBy(xpath = "//div[contains(@class, 'result')]")
- 87. ...
- 88. }
- 90. Android 1.x not supported
- 91. Android 2.x – phones
- 92. Android 3.x – tablets
- 93. Android 4.x – phones and tablets
- 94. Physical device vs. emulator
- 96. Linux – set up udev
- 97. Mac OS X – no setup needed
- 99. Android 1.5 – 4.0.3
- 101. Eclipse plugins
- 104. Works well with newest Selenium
- 105. Demo Creating and launching a new emulator
- 107. Project porting Android to x86 platform
- 108. Demo Launching Android in VirtualBox
- 110. <property name="implementationClass"> org.openqa.selenium.android.AndroidDriver </property>
- 113. </property>
- 114. </extension>
- 116. Launch WebDriver application in emulator
- 117. platform-tools/adb forward tcp:4444 tcp:8080
- 118. Use 10.0.2.2 for host's localhost
- 122. Launch WebDriver application in emulator
- 123. platform-tools/adb forward tcp:4444 tcp:8080
- 124. Tests need server IP address
- 125. Demo Tests running with Firefox, Android emulator and Android-x86
- 128. JBoss Tools
- 129. m2e
- 131. Demo Running tests in Eclipse
- 133. Demo Debugging
- 135. Hot news!
- 136. Create emulator
- 137. Start emulator
- 139. Start Android server
- 140. Can connect to real device
- 149. public abstract class AbstractWebDriverTest<P extends Page> extends Arquillian {
- 150. ...
- 151. }
- 153. public void handleTestError(ITestResult result) {
- 154. if (result.getStatus() == ITestResult.SUCCESS) {
- 155. return;
- 156. }
- 157. ...
- 158. File scrFile = ((TakesScreenshot) driver).getScreenshotAs(OutputType.FILE);
- 160. }
- 164. Simulates mobile phones and tablets
- 165. Perfect for layout testing
- 166. Not for automation
- 169. Run from console and Eclipse
- 170. How to create Android emulator
- 171. Android-x86
- 172. Emulator snapshots
- 173. ID locators, Xpath locators, CSS locators
Hinweis der Redaktion
- Smart phones Laptops 209.6 Desktops 112.4 Tablets 63.2 Netbooks 29.4
- Karel showed you what Arquillian is, what it can do ... He showed Drone extension – WebDriver, Selenium, Ajocado I'll show you how we test RichFaces, a Java Server Faces web framework using Arq on desktop in various browsers I'll explain you how we use all the technologies on this slide for testing Then, after you will get familiar with testing web applications on desktop, I'll introduce you to testing on mobile devices (Android) First I'll show you how to test in emulator and then how to speed up your tests Ajocado – works with Selenium 1 which doesn't support mobile browsers
- When you need to test your Java web app, you need to build your application and create a WAR archive which can be then deployed to a container In last talk Karel showed you how to start a container and deploy you application According to the version of Selenium you are using, you need to start Selenium server Selenium uses JavaScript to automate web pages. runs inside the JavaScript sandbox, Selenium-RC server to get around the same-origin policy, can sometimes cause issues with browser setup WebDriver on the other hand uses native automation from each language. While this means it takes longer to support new browsers/languages, it does offer a much closer ‘feel’ to the browser. If you’re happy with WebDriver, stick with it, it’s the future. There are limitations and bugs right now, but if they’re not stopping you, go for it. Open web browsers – Selenium 2 supports all major browsers run your tests – TestNG / Junit, integration with Arq, Jenkins Review test results – TestNG report, Jenkins plugin for TestNG
- Sample RichFaces 4 application built using latest Java EE 6 technologies – JSF2, RichFaces 4, CDI, Bean validation Currency converted which converts 30+ currencies from/to Euros Currency converter, exchange rates list, historical chart Downloads data from ECB Tested on JBoss AS 7.0.2 and 7.1.0.Final released this week Screenshot of desktop version
- This uses default testng.xml
- Since it is split, it allows us to run tests multiple times on Jenkins i.e. Unit tests once Functional tests with every container and browser Not implemented yet, just a proof of concept
- You can either use prepared package or construct war yourself If want to use prepared package, you need to run tests after Maven phase package
- You can either use prepared package or construct war yourself If want to use prepared package, you need to run tests after Maven phase package
- Include all classes All xhtml files All images, javascript, css All descriptors, e.g. Bean.xml, web.xml, faces-config.xml All Maven dependencies
- You can use whichever driver that is supported by Drone Firefox Chrome Internet Explorer Android We didn't test OperaDriver yet
- Althought simple webdriver test might look like this, it's is better to use page factory pattern for creating tests
- Do you still remember mobile version of RichRates? If we implemented test using page objects, such a object could Select a date Insert an amount Click the “Calculate” button Select a currency Swap currencies Verify the result of calculation
- I focus on emulators because we need to run our tests in continuous integration server (Jenkins) and physical devices don't scale
- As you could see, it is not very fast, mainly because it is an emulator – it emulate an ARM processor. However, there is a solution which can speed up your Android.
- You can download several prepared images which you can install to a virtual machine, e.g. VirtualBox I tried both Android 3.2 and 4.0 4.0 latest release doesn't work, can be installed but cannot be started Nightly build of 4.0 works like a charm I used an image for Asus EEE, it's netbook but I set up it to have lower resolution so it behaves like a mobile phone It's not ARM but good enough for testing web Fast !!! Unfortunately not as fast as desktop browsers
- The only drawback is that it sends user agent string as a tablet so e.g. Google serves you a tablet version of search
- Android-server-2.6.0.apk for Android 2.2,2.3 Android-server-newest.apk for Android 3+
- Arquillian TestNG tests are fully supported by TestNG Eclipse plugin so it's possible to run whole test suite, selected class or selected method
- Since TestNG is supported well in Eclipse, debugging is very easy. One can debug tests running in both emulator and android-x86
- Android eclipse plugin helps a lot with creating new emulators, starting them etc However, it is manual process. Karel created Arq extension that can automate also this part of testing. It was created last week so it's still hot. Unfortunately, we didn't manage to integrate it to RichRates application.
- Unit tests should run very fast so it doesn't make sense to log which tests is running...it would slower test execution. On the other hand, functional tests usually run much longer (on Android even few seconds). We find it useful to be able to watch test execution progress, especially on Jenkins.
- After method, always run Result status check Captures screenshots on all major browsers including Android Screenshot contains whole page, not only visible area Dalo by sa implementovat ako Testng listener?
- Currently we use android plugin on Jenkins You need to install Android SDK on Jenkins slave We run a script that deploys android-server.apk and runs the application