Changes between Version 6 and Version 7 of SCS_TEST_TRACKING_MAINTENANCE_R4

Timestamp:

07/04/09 13:33:05 (16 years ago)

Author:

deyan

Comment:

--

SCS_TEST_TRACKING_MAINTENANCE_R4

@@ -32 +32 @@
  * App file dialogs test case should be split for the various file dialogs. All of them should be covered. Consisitency should be ensured. #1714
  * Embedding book test case should include embedding the book twice. Probably a new test case ensuring the resources can be duplicated will be OK. #1722
+ * A persistence test case is needed. This can be done by a general test case covering most of the functionality or split into pieces (Each functionality test case to include save and reload. If one test case is created, it should be regular. #1725, #1726, #1727, #1728, #1729 ...
+  * A good idea is to create one fast test - that tests persistence of all elements, and then tests for specific things, that should be tested if the master test fails.
 = Implementation =
 ^(Describe and link the implementation results here (from the wiki or the repository).)^