Changes between Version 3 and Version 4 of SCS_TEST_TRACKING_MAINTENANCE_R0

Timestamp:

09/30/08 14:35:52 (17 years ago)

Author:

deyan

Comment:

--

SCS_TEST_TRACKING_MAINTENANCE_R0

@@ -4 +4 @@
 Maintenance depends on test tracking setup. The maintenance should be performed monthly. 
 == Task requirements ==
+These task requirements apply for all revisions. Please expand them in other revisions' analysis.
  * Review existing tests.
  * Review test current progress. Discuss with team problem tests.
@@ -12 +13 @@
 The result should be stored in a log file in the wiki for example. Decide if this is the best way to keep information about maintained tracker.
 == Implementation idea ==
-Create [wiki:SCS_TEST_TRACKING_MAINTAINCE] and split it into 12 sections. Name each section with milestone and date. Fill in first section (for this milestone). Define rules about this document.
+Create [wiki:SCS_TEST_TRACKING_MAINTAINCE] and split it into 12 sections. Name each section with milestone and date. Fill in first section (for this milestone). Define rules about this document. Otherwise fill in Implementation section what is done.
 == Related ==
 [wiki:SCS_TEST_TRACKING_SETUP_R0]
 == How to demo ==
-You should be able to present task progress by showing [wiki:SCS_TEST_TRACKING_MAINTAINCE]
+You should be able to present task progress by showing [wiki:SCS_TEST_TRACKING_MAINTAINCE_R0#Implementing]
 = Design =
-Currently, tcw is set up but there are only example tests. Make sure test tracker is working properly and delete existing test cases.
+Decided to use current revision's implementation section (see Implementation Idea).Currently, tcw is set up but there are only example tests. Make sure test tracker is working properly and delete existing example test cases.
 = Implementation =
-
+Deleted two existing web cases. Ensured tcw is working properly and is not visible from outside due to security issues. Test tracker is now empty and set up for internal use.
 = Testing =