Analysis
Overview
This Iteration should start filling in tests for manual testing of tasks, that allow manual testing.
Task requirements
- Resetup Testlink or suggest a solution for migrating the database to a new machine.
- Propose solution for integration between testlink and trac
- Create user accounts for the team in http://62.44.108.3/testlink
- Discuss the current structure of testlink cases with the team and apply improvements if needed.
- Review iteration pages for 01 and 02 and propose tasks that are allowing manual testing.
- Present the requirements for the test cases on a meeting
Task result
Working migratable test tracking server and requirements for the test cases
Implementation idea
- Design
- Research if it is possible to migrate the current testlink installation (0.1 ef)
- Research ways to integrate trac with testlink. Probably a macro in the wiki will be convinient (0.5 ef)
- Implementation
- Create user accounts for developers (0.1 ef)
- Discuss current structure with the team and modify it if needed (0.5 ef)
- Create a wiki page with tasks from i01 and i02 that require testing, discuss them with the team and create empty test cases for these tasks. Create test plans for different iterations, create builds and look for custom fields integration with trac (0.5 ef)
- Create a draft page with rules or link existing manual test cases rules.
Related
http://62.44.108.3/testlink/index.php
PLATFORM_STANDARDS_MANUAL_TESTS_R0
How to demo
Show user accounts and empty test cases in http://62.44.108.3/testlink/index.php
Design
- These tasks should be revised and choose which of them will be tested: UNPLANNED_TEST_TRACKING_MAINTENANCE_R1b/ManualTests. Delete the unneccessary ones.
- The current setup will be used for now, later the database will be migrated to another machine.
- See the accounts in trac,
- Create accounts for developers with the same dev ids and a default password
- Choose permissions to those accounts
- Send an e-mail to the dev-list and ask the developers to visit testlink and change their passwords
- Use current structure, create a forum topic and send an email to the dev list to discuss the structure.
- Link existing platforms standards for manual test cases
- Separate the tasks from UNPLANNED_TEST_TRACKING_MAINTENANCE_R1b/ManualTests
- Choose tasks that will be included as test cases
- Choose the tasks for discussion
- Choose 4-5 tasks and describe steps and results for testing, create a test plan and execute the tests.
- If there is time left, see custom fields and possibilities to provide integration between trac and the wiki.
Implementation
- The server is set up at http://62.44.108.3/testlink
- Created user accounts for almost each team member.
- Chosen tasks that will be included as test cases
- Chosen few tasks that will be included as test case prototypes (Note that this one is part of the test phase of these tasks)
- Created a forum topic here: 15
- Sent an e-mail with accounts and structure information.
- Below are chosen tasks for testing, the differences between this list and UNPLANNED_TEST_TRACKING_MAINTENANCE_R1b/ManualTests should be discussed before next revision.
Tasks that will be included as empty test cases
BASE_BOUND_CONTROLS_R0
PLATFORM_DEPLOYMENT_BUILD_ECLIPSE_R0
APP_MAIN_WINDOW_R0
BOOK_WINDOW_R0
PLATFORM_NFR_COMPATIBILITY
SCS_MACHINE_SETUP_R0
SCS_BACKUP_R0
PLATFORM_DEPLOYMENT_BUILD_MAVEN_R0
PLATFORM_DEPLOYMENT_BUILD_ANT_R0
APP_PLUGIN_STARTUP_R0
PLUGIN_EDITIONS_STRUCTURE_R1
SCS_ISSUE_TRACKER_SETUP_R1
SCS_TEST_TRACKING_SETUP_R1
SCENE_COMMONS_R0
PRO_LIB_INSPECTOR_R0
BASE_DIALOGS_R0
BOOK_BOTTOM_PANEL_R0
CORE_LOGGING_R0
PAGE_SELECTOR_R0
These tasks will have test case prototypes
SCS_ISSUE_TRACKER_SETUP_R0
S2S_WEB_COMMONS_R0
SCS_REPO_MIGRATE_R0
Added all these as test cases. They should be corrected if needed in testing phase of corresponding tasks.
Testing
Comments
(Write comments for this or later revisions here.)