Version 9 (modified by deyan, 16 years ago) (diff) |
---|
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://10.10.117.11/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://10.10.117.11/testlink/index.php
PLATFORM_STANDARDS_MANUAL_TESTS_R0
How to demo
Show user accounts and empty test cases in http://10.10.117.11/testlink/index.php
Design
- These tasks should be revised and choose which of them will be tested: 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
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)