[[BackLinksMenu]]

= Analysis =
== Overview ==
We are going to use our test tracking system for maintaining our manual tests and finding bugs and linking them with bug tracking system. For this revision of the task we've got several things to do that are listed in the section below.
== Task requirements ==
Because of the security issues that appeared in tcw we must either:
 * improve tcw security
or
 * find a better solution for tracking of the manual tests and integrate it
== Task result ==
The result of this task must be functional test tracking system with the necessary security.
== Implementation idea ==
 * research for other test tracking systems
 * compare them with tcw
 * decide which will be best for our purposes and integrate it
 * or find a solution to tcw security issues that are concerning us
== Related ==
[wiki:SCS_TEST_TRACKING_SETUP_R0] [[BR]]
[wiki:SCS_TEST_TRACKING_MAINTENANCE_R0] [[BR]]
[wiki:SCS_TEST_TRACKING_MAINTENANCE_R1] [[BR]]
== How to demo ==
Open the test tracking system. Show sample test case (there are some available at the moment).

= Design =
What have to be done?
 * Research different tracking solutions. 
 * Choose an applicable and explain why it is better than the others.
 * Give link and setup instructions
 * Define user creation, permissions, etc
Tested TestLink 1.7.4 stable release. Benefits:
 * Web based 
 * Easy install
 * Covers all the functionalities of TCW [[BR]]
Minuses:
 * Should run a SMTP server
 * 
 
= Implementation =
^(Implementation results should be described and linked here (from the wiki or the repository))^

= Testing =

= Comments =

= Log =
[[Include(wiki:SCS_TEST_TRACKING_SETUP_R1_LOG)]]