{"id":34100,"date":"2016-05-02T14:58:10","date_gmt":"2016-05-02T09:28:10","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=34100"},"modified":"2016-12-19T15:02:53","modified_gmt":"2016-12-19T09:32:53","slug":"how-to-provide-your-testsscripts-dependencies-to-aws-device-farm","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/how-to-provide-your-testsscripts-dependencies-to-aws-device-farm\/","title":{"rendered":"How to provide your TestsScripts & Dependencies to AWS Device Farm"},"content":{"rendered":"

If you are using Appium, TestNG & Maven test frameworks and Java language for your mobile automation<\/a> project, then it’ll help you.<\/p>\n

To run your Appium Java TestNG scripts,\u00a0you need to club your test-cases & all the dependencies in one file and provide it to Device Farm. And to attain this,\u00a0do some modifications in the pom.xml<\/strong> file in your project.<\/p>\n

i)\u00a0Set packaging as a JAR file:<\/h3>\n

[java]
\n<groupId>com.acme<\/groupId>
\n<artifactId>acme-android-appium<\/artifactId>
\n<version>1.0-SNAPSHOT<\/version>
\n<packaging>jar<\/packaging>
\n[\/java]<\/p>\n

ii)\u00a0Include maven-jar-plugin to build your tests into a JAR file:<\/h3>\n

This plugin will build your test source code (anything on this path\u00a0src\/test directory) into a JAR file.<\/p>\n

[java]
\n<plugin>
\n <groupId>org.apache.maven.plugins<\/groupId>
\n <artifactId>maven-jar-plugin<\/artifactId>
\n <version>2.6<\/version>
\n <executions>
\n <execution>
\n <goals>
\n <goal>test-jar<\/goal>
\n <\/goals>
\n <\/execution>
\n <\/executions>
\n<\/plugin>
\n[\/java]<\/p>\n

 <\/p>\n

iii)\u00a0Use maven-dependency-plugin which will build all the dependencies as JAR files:<\/h3>\n

[java]
\n<plugin>
\n <groupId>org.apache.maven.plugins<\/groupId>
\n <artifactId>maven-dependency-plugin<\/artifactId>
\n <version>2.10<\/version>
\n <executions>
\n <execution>
\n <id>copy-dependencies<\/id>
\n <phase>package<\/phase>
\n <goals>
\n <goal>copy-dependencies<\/goal>
\n <\/goals>
\n <configuration>
\n <outputDirectory>${project.build.directory}\/dependency-jars\/<\/outputDirectory>
\n <\/configuration>
\n <\/execution>
\n <\/executions>
\n<\/plugin>
\n[\/java]<\/p>\n

iv) Now save the following XML assembly to this path (src\/main\/assembly\/zip.xml).<\/h3>\n

This XML is an assembly definition which will instructs Maven to build a .zip file containing everything in the root of your build output directory and the dependency-jars directory:<\/p>\n

[java]
\n<assembly
\n xmlns="http:\/\/maven.apache.org\/plugins\/maven-assembly-plugin\/assembly\/1.1.0"
\n xmlns:xsi="http:\/\/www.w3.org\/2001\/XMLSchema-instance"
\n xsi:schemaLocation="http:\/\/maven.apache.org\/plugins\/maven-assembly-plugin\/assembly\/1.1.0 ;
\n <id>zip<\/id>
\n <formats>
\n <format>zip<\/format>
\n <\/formats>
\n <includeBaseDirectory>false<\/includeBaseDirectory>
\n <fileSets>
\n <fileSet>
\n <directory>${project.build.directory}<\/directory>
\n <outputDirectory>.\/<\/outputDirectory>
\n <includes>
\n <include>*.jar<\/include>
\n <\/includes>
\n <\/fileSet>
\n <fileSet>
\n <directory>${project.build.directory}<\/directory>
\n <outputDirectory>.\/<\/outputDirectory>
\n <includes>
\n <include>\/dependency-jars\/<\/include>
\n <\/includes>
\n <\/fileSet>
\n <\/fileSets>
\n<\/assembly>
\n[\/java]<\/p>\n

 <\/p>\n

v)\u00a0Use maven-assembly-plugin\u00a0to club all the test cases and dependencies:<\/h3>\n

Now after adding the above assemble, use this plugin maven-assembly-plugin which will package all tests and dependencies into a single .zip file.<\/p>\n

[java]
\n<plugin>
\n <artifactId>maven-assembly-plugin<\/artifactId>
\n <version>2.5.4<\/version>
\n <executions>
\n <execution>
\n <phase>package<\/phase>
\n <goals>
\n <goal>single<\/goal>
\n <\/goals>
\n <configuration>
\n <finalName>zip-with-dependencies<\/finalName>
\n <appendAssemblyId>false<\/appendAssemblyId>
\n <descriptors>
\n <descriptor>src\/main\/assembly\/zip.xml<\/descriptor>
\n <\/descriptors>
\n <\/configuration>
\n <\/execution>
\n <\/executions>
\n<\/plugin>
\n[\/java]<\/p>\n

 <\/p>\n

vi) At Last, build the package with the following command<\/h3>\n

In command prompt & the directory should be that where pom.xml file exist:<\/p>\n

[java]mvn clean package -DskipTests=true[\/java]<\/p>\n

After successful build, you can check the\u00a0target<\/strong> folder, all your test-cases & dependencies have been club in single .zip file\u00a0named zip-with-dependencies.zip<\/strong><\/p>\n

\"targetFolder\"
\nThen use this file to automate your test-cases on AWS\u00a0Device Farm: \u00a0on the Configure test page<\/strong>, choose Appium Java TestNG<\/strong> as test suite and Upload<\/strong>\u00a0this file\u00a0‘zip-with-dependencies.zip’ and Enjoy your test-suite on multiple\u00a0devices in\u00a0parallel. \ud83d\ude42<\/p>\n

\"uploadDependencies\"<\/p>\n","protected":false},"excerpt":{"rendered":"

If you are using Appium, TestNG & Maven test frameworks and Java language for your mobile automation project, then it’ll help you. To run your Appium Java TestNG scripts,\u00a0you need to club your test-cases & all the dependencies in one file and provide it to Device Farm. And to attain this,\u00a0do some modifications in the […]<\/p>\n","protected":false},"author":201,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":29,"footnotes":""},"categories":[518,1818,1174,1772,1816],"tags":[1978,1979,3274],"class_list":["post-34100","post","type-post","status-publish","format-standard","hentry","category-android","category-automation-testing-testing-2","category-aws-2","category-mobility","category-testing-2","tag-android-app-testing","tag-app-automation-testing","tag-appiumtestng"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t