SCS_TEST_TRACKING_MAINTENANCE_R1

[Astea]

wiki page: SCS_TEST_TRACKING_MAINTENANCE_R1 - effort: 0.5d

[[BackLinksMenu]]

= Analysis =
== Overview ==
Enter some tests script. They should be connected with tasks form the previous iteration.
== Task requirements ==
Create accounts for the developers in tcw.
Create a structure of tcw - Parent test cases. Include test cases for tasks that allow tests from previous iteration.
Tasks from the previous iteration that can be included as test cases:[[BR]]
[wiki:BASE_BOUND_CONTROLS_R0][[BR]]
[wiki:APP_MAIN_WINDOW_R0][[BR]]
[wiki:SCS_REPO_MIGRATE_R0][[BR]]
[wiki:SCS_SITE_DESIGN_R0][[BR]]
[wiki:SCS_FORUM_R0][[BR]]
As testing SCS by creating, filling in and deleting items is not convenient, it may be added as a single test. Create an e-mail for the community server troubles, decide using current dev mail list or create a forum topic. 

== Task result ==
A test tracking structure(Parent tasks). >=3 usable test cases satisfying rules from [wiki:PLATFORM_STANDARDS_MANUAL_TESTS_R0]. Parent test cases should be needed. 
== Implementation idea ==
Structure:
{{{
Sophie2
|-Sophie2
|--Platform
|--Core
|--Base
|--Main
|--Extra
|--S2S
|-SCS
}}}
See [source:/manage/sched/sophie2-wbs.py] and put test cases from Task requirements section into appropriate place in the structure. 
== Related ==
[wiki:SCS_TEST_TRACKING_MAINTENANCE_R0]

== How to demo ==
Show the structure in tcw and created test cases.

= Design =
Apply the structure.
{{{
Sophie2
|-Sophie2
|--Platform
|--Core
|--Base
|--Main
|--Extra
|--S2S
|-SCS
}}}
Check the python file and create required sections. Create administrator accounts for each team member. Create a forum topic with community server testing instructions.
= Implementation =
http://10.10.117.11/tcw/login.php
Created the structure from implementation idea. Created following administrator accounts: "todor, deyan, pav, pap, pac, tanya, peko, milo, steve, dan". Ask for the password. Created 3 test cases - Bound Controls, APP_MAIN_WINDOW and Basic SCS features. Considering this task done, describing the test cases should be done after test phase for these tasks are done. Added [topic:12 Forum Topic]

= Testing =

= Comments =

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

Edit
Edit Log

[deyan]

analysis and design passed, migrating to new workflow format

[deyan]

analysis and design passed, migrating to new workflow format

[deyan]

3.5p analysis and design passed, migrating to new workflow format

[deyan]

analysis and design passed, migrating to new workflow format

[deyan]

analysis and design passed, migrating to new workflow format

[deyan]

3p analysis and design passed, migrating to new workflow format

[todor]

2 by todor. The structure of design does not satisfy the requirements for design, copy part of the implementation ideas there if it is necessary. In the implementation part of the task there is no link to the result of this task, which makes its reviewing hard. One of the task requirements (mail to the dev group) is not fulfilled.

[deyan]

"Review: 2 by todor."Is this a review or a superreview? this design has already passed review, i am not refactoring it until it is clear.

[todor]

Replying to deyan:

"Review: 2 by todor."Is this a review or a superreview? this design has already passed review, i am not refactoring it until it is clear.

It's review of the implementation, this suppose reviewing both design and implementation.

[deyan]

design changed

[deyan]

expanding implementation

[deyan]

expanding implementation

[deyan]

done 30m

[pap]

Review: 3. It's generally good but please change the link so that it uses domain names instead of IP addresses. Also 5/12 means nothing to me so please use more explanatory sentences.

[deyan]

repairing from invalid state

[deyan]

added an,de,im owners

[deyan]

Batch update from file newimport.csv

[deyan]

Batch update from file query-obsoleted.csv