Changes between Version 6 and Version 7 of PLATFORM_STANDARDS_AUTO_TESTS_R1

Timestamp:

01/16/09 16:15:04 (16 years ago)

Author:

boyan

Comment:

--

PLATFORM_STANDARDS_AUTO_TESTS_R1

@@ -65 +65 @@
 |___Reviewing
 |__Running tests
+|__GUI testing
 |__Useful links
 |_Comments
@@ -76 +77 @@
   * Reviewing - how to judge if a given test is good enough; how to review the testing phase of tasks.
  * Running tests - a description of how to run a given test or all tests (via Maven or Hudson).
+ * GUI Testing - a how-to of testing the user interface.
  * Useful links - Links for further reading on the topic.
  * Comments - Comments for improving the standards that will be incorporated into the page in the next revision.
 
 Everyone has been asked to give suggestions for improving the standards in the Comments section. These will be considered in the implementation phase.
+
+Research has been made on the various GUI testing libraries, starting with the following resources:[[BR]]
+http://asteasolutions.net/mediawiki/index.php/Sophie-JR-Research-SwingUnitTesting [[BR]]
+http://www.junit.org/taxonomy/term/6 [[BR]]
+It seems that Abbot (http://abbot.sourceforge.net/doc/overview.shtml) is the best choice that suits our needs:
+ * It is based on JUnit and should be easily integrated in Hudson.
+ * It provides a way to add assertions for things on a modal dialog.
+ * There is plenty of documentation and getting started with it should be relatively easy.
+One of the other high-ranked choices, UISpec4J, is reported to have problems with the integration with Hudson and running under Linux as a whole.[[BR]]
+A how-to of using Abbot will be provided in the implementation.
 
 = Implementation =