Coder Social home page Coder Social logo

android-testng's People

Contributors

jfcamel avatar pfumagalli avatar tkcmrc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

android-testng's Issues

XML results file

Hi there! Is there a way to quickly configure the TestNGRunner to generate an XML results file after tests are completed? I would like to do this to be able to simply pull the XML results from the device for publishing in Jenkins. I'd prefer not to use the results file generated by Gradle because there might not be a device connected to the node used to build the tests and the app (but there might a slave node with the devices connected that runs the job to run the tests).

AndroidTestNGSupport not having "injectInstrumentation" called

Hi,
For a default configuration of android-testng, any tests run will encounter "java.lang.IllegalStateException: No Android instrumentation available" during a call to the AndroidTestNGSupport.getContext method because AndroidTestNGSupport.injectInstrumentation is not ever previously injecting an instrumentation instance into the class.

TestNG unable to find tests in classpath

Hi,
I've encountered an issue trying to run instrumentation tests that I've replicated on the instrumentation tests in your own repository. Although building the project is successful, the following runtime error occurs (in this example, when running the "AndroidComponentsTest" test):

org.testng.TestNGException:
Cannot find class in classpath: de.lemona.android.testng.test.AndroidComponentsTest
at org.testng.xml.XmlClass.loadClass(XmlClass.java:81)
at org.testng.xml.XmlClass.init(XmlClass.java:73)
at org.testng.xml.XmlClass.(XmlClass.java:59)
at org.testng.xml.TestNGContentHandler.startElement(TestNGContentHandler.java:544)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
...

I've tried fixing this issue by adding a testng.xml file specifying the test path, but it didnt solve the issue.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.