Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the zip file of appium ? #26

Open
NateZ7 opened this issue Mar 18, 2018 · 5 comments
Open

What is the zip file of appium ? #26

NateZ7 opened this issue Mar 18, 2018 · 5 comments

Comments

@NateZ7
Copy link

NateZ7 commented Mar 18, 2018

In the gradle plugin there is this part:

appium {
    tests file("path to zip file") // Required
    useTestNG() // or useJUnit()
}

What is the path to zip file ?
I'm using gradle of course.
Thanks!

@JinZgitH
Copy link

The zip file is your test package.
and you can find more information at https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types-intro.html
hope that helps

@satheeshkumarf
Copy link

satheeshkumarf commented Aug 26, 2018

Hi Guys, Any idea about generating the single jar file with all tests info, using gradle builds? instead of maven build

@jamesknowsbest
Copy link

@satheeshkumarf does this help to answer the inquiry?
https://stackoverflow.com/a/52398377/8016330

@Dorme
Copy link

Dorme commented Jun 8, 2019

I'm still unable to create a zip file with the link provided above. When I use from sourceSets.test.runtimeClasspath, I get this error:
"ERROR: Could not get unknown property 'test' for SourceSet container of type org.gradle.api.internal.tasks.DefaultSourceSetContainer."
My code is located under: app/src/test

I've tried replacing these by from 'src/test/java' and then I'm able to create a zip file. But when I use the zip file in AWS Device Farm, I'm getting this:
There was a problem processing your file. We could not find a class file within the tests JAR file. Please unzip your test package and then unjar the tests JAR file, verify that at least one class file is within the JAR file, and try again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants