Lines Matching +full:- +full:- +full:junit +full:- +full:xml

4 * Allow a testng.xml file to be passed when -testjar is used
8 * Make it possible to specify groups on command line and classes in testng.xml
9 (and any combinations thereof:  command line, ant, testng.xml)
10 * DataProvider index in testng.xml
12 * Add time-outs at the testng.xml.  Also:  test and suite time-outs? http://tinyurl.com/kbwxq
15 * Make it possible to add listeners from the Eclipse plug-in
26 * Multi-threading for invocationCount and maybe for <test> too
32 * testng-dist.zip should contain a top-level directory
39 * Improve the plug-in API so people can add listeners without having to
57 avoid having to use testng.xml
79 * Support multiple testng.xml (TestNG allows it but not the reporters
83 * testng-failed.xml should contain the parameters of testng.xml (if any)
84 * Create a testng-failed.xml that includes dependent methods
86 easier reporter for "slowest method first" or generate testng-failed.xml
89 - build.xml should issue a clear error message if trying to build with JDK1.4
90 - Implement <tasdkdef resource="testnganttasks"> so we can define
92 - Write documentation to declare ant task in section 3.2.8
93 - Documentation for alwaysRun
94 - Allow to specify packages or prefix in the <classes> tag:
96 - New assert classes
97 - New ways to launch 
98 - JUnitConverter documentation
99 - new beforeSuite/afterSuite
101 * in testng-failures.xml include the beforeSuite/afterSuite methods (very tricky)
104 * Make timeOut() work in non-parallel mode (the default mode needs to become
105 parallel=true thread-count=1
111 Make TestNG run on class files and not just on testng.xml
112 Make TestNG run on a jar file that has a testng.xml file in its root or just on all
126   JUnit adapter
145 For whatever its worth, here are my problems with JUnit.  I've largely developed work-arounds.
147 1. Interface-based testing is awkward.
148 2. Only fast-fail tests are supported.
151 How should interface-based testing be handled in TestNG?  A nice feature would be bundled tests for…
152 - all classes will fail a (supressible) test if they violate the contract for equals() and hashCode…
153 - classes that implement Comparable will fail a test if they fail to implement Comparable
154 - and likewise for java.io.Serializable, java.util.Map, java.util.List, etc...
156 When I say all tests are fast-fail in JUnit, what I mean is that the first failed assertion in a me…
158 …-arounds for doing these in JUnit, but developing tools for conversational tests that play nice wi…