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:
BASE_BOUND_CONTROLS_R0
APP_MAIN_WINDOW_R0
SCS_REPO_MIGRATE_R0
SCS_SITE_DESIGN_R0
SCS_FORUM_R0
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 PLATFORM_STANDARDS_MANUAL_TESTS_R0. Parent test cases should be needed.

Implementation idea

Structure:

Sophie2
|-Sophie2
|--Platform
|--Core
|--Base
|--Main
|--Extra
|--S2S
|-SCS

See manage/sched/sophie2-wbs.py and put test cases from Task requirements section into appropriate place in the structure.

Related

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 Forum Topic

Testing

Comments

Log

Analysis: deyan (done:45m)
Review: 3.5 by Pav (done:10m)
Design: deyan (done:5m)
Review: 3 by Pav(done:10m) It has to be more detailed. Use bullets for better reading.
Implementation: deyan (done)
Review: 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.
Implementation2: deyan (done:30m)
Review: 3 by Pap. 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.
Testing:
Comments:"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.
Comment2: The implementation review supposes that both design and implementation must be reviewed in order to pass the task.