• XPTest 2.2
  • It is now possible again to create JUnit-based TestPackage classes. This feature was not available in the last version if 'JUnit-compatibility' was turned on.

  
  

  XPTest 2.1

  • Unfortunately, during the development of XPTest 2.0 in cooperation with TogetherSoft, there has been no change history. Mainly the configuration UI has been rewritten and a new testsupport module has been implemented. The code generation has also been overhauled. Now my CVS server will be the central repository for new versions again, so there will be a changelog again.

  
  

  XPTest 1.5

  • removed some slashes in javadoc.xml for ant to achieve JDK 1.2.2 compatibility (thanks to H. Schmidt)

  
  

  XPTest 1.4

  • Switched to cross-platform look & feel to avoid problems with Together scrollbars on Windows.

  • Test classes names now named Test<TestedClass> instead of <TestedClass>Test

  • Enabled the generation of suite() methods

  • Fixed broken comment inside generated test methods

  • Fixed NullPointerException resulting from the creation of a class pair using the TestCase pattern

  • Added a warning message if JUnitX is not in the Classpath if a TestCase is created. Thus there will be no more problems with TestPackage classes not collecting test cases because the test cases do not extend junit.framework.TestCase.

  • Generated code will no be specifically fro JUnitX. For JUnit 3.2 some statements need to be changes. Since JUnitX is a superset of JUnit nobody should have a problem changing from JUnit to JUnitX.

  • Pattern links between tested classes and their test cases are currently not hidden since Together only sometimes hides the link. As I get more information on the OpenAPI I will try to hide them again.

  • All generated classes have comments now

  • Fixed the misplaced icon in the TestCase pattern dialog resulting from a on-line string in a multi-line typed field

  • Added stereotype <<tested>> to tested classes

  • Changed the generated code of TestPackage classes to match the new JUnitX-style test packages. Especially all collected tests are referenced including their full package names.

  • Added multiple choice option for the test case placement strategy in the configuration dialog. Now test cases will be created in the same package, a subpackage or in a parallel package hierarchy of the production classes.

  • The AWT UI from JUnit has been dropped completely

  • Added a help window to the configuration dialog.

  • Refactored the complete source and splitted big classes into several small classes for example

  • Documented the source

  • Updated the HTML description pages for all patterns.

  • Depending on the strategy for placing test cases, a suitable destination package will now be proposed in the TestCase Pattern dialog

  • Destination packages will be created automatically for test cases, if the necessary packages do not exist

  • The last configuration of every pattern will be stored and used to initialize it's configuration dialog the next time

  • Added the TestProxy pattern necessary to access protected or private code. TestProxies will be created automatically when the option 'private code tests' is enabled in the TestCase pattern configuration dialog.

  • Added options to the XP context menu to create patterns based on their last configuration

  • Added hotkeys to all important context menu options

  • Unaccessible stdout and stderr logfiles of Together are now handled gracefully with a warning message

  • Included the javadoc documentation in the distribution

  • Added ant.bat script and switched from build.sh to ant.sh script

  • Wrote a tutorial which is included in the distribution

  • renamed XPTest configuration file to XPTest.properties.

  • Added experimental support for catching stdout/stderr of JUnitX on Windows.

  • Replaced the tutorial by a complete example showing the features of new XPTest version.

  • Support for renamed stdout logfiles on Unix for Together 4.2.

© 2001 A. Heilwagen