Views
Quality/Test management overview
From MeeGo wiki
(Difference between revisions)
m (→Automated Testing) |
|||
| Line 3: | Line 3: | ||
== Manual and Semi-automated Testing == | == Manual and Semi-automated Testing == | ||
| - | [[File:Test_management_manual_semi.png]] | + | The main phases for manual and semi-automated testing are test planning, execution and reporting. |
| + | |||
| + | The figure below illustrates the process. The process is explained in more detail after the figure. | ||
| + | |||
| + | [[File:Test_management_manual_semi.png|800px]] | ||
| + | |||
| + | '''Test Planning''' | ||
| + | |||
| + | * [[Quality/QA-tools/Test_plan|Test plans]] are created and edited by using [[Quality/QA-tools/Testplanner|Testplanner]] | ||
| + | ** The test cases can be linked to specific bug and feature ID's | ||
| + | * The created test plans are avalaible at Gitorious repositories | ||
| + | ** In addition to plain XML format, the test plans can also be viewed in more user-friendly format as presented at [http://testplans.meego.com/ testplans.meego.com/] | ||
| + | * Since Gitorious is a version control system, the plans can be used and edited by several users | ||
| + | * Weekly test management meeting decides which tests are to be executed | ||
| + | |||
| + | '''Test Execution''' | ||
| + | |||
| + | * The tests can be executed by several test engineers by using different execution tools | ||
| + | ** Testing can be done manually or by using automated testing environment [[Quality/QA-tools/OTS|OTS]] | ||
| + | * The testing is done by using agreed MeeGo release | ||
| + | * [[Quality/QA-tools/Testrunner|Testrunner]] and [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] are tools that can execute test plan files and produce results in specified [http://meego.gitorious.org/meego-quality-assurance/test-definition/blobs/master/src/data/testdefinition-results.xsd XML format] | ||
| + | |||
| + | '''Test Reporting''' | ||
| + | |||
| + | * The results can be published at [http://qa-reports.meego.com qa-reports.meego.com] either manually or automatically | ||
| + | * The report shows the results for each test case and for each feature or bug | ||
== Automated Testing == | == Automated Testing == | ||
Revision as of 08:42, 29 December 2010
Test Management Overview
Manual and Semi-automated Testing
The main phases for manual and semi-automated testing are test planning, execution and reporting.
The figure below illustrates the process. The process is explained in more detail after the figure.
Test Planning
- Test plans are created and edited by using Testplanner
- The test cases can be linked to specific bug and feature ID's
- The created test plans are avalaible at Gitorious repositories
- In addition to plain XML format, the test plans can also be viewed in more user-friendly format as presented at testplans.meego.com/
- Since Gitorious is a version control system, the plans can be used and edited by several users
- Weekly test management meeting decides which tests are to be executed
Test Execution
- The tests can be executed by several test engineers by using different execution tools
- Testing can be done manually or by using automated testing environment OTS
- The testing is done by using agreed MeeGo release
- Testrunner and testrunner-lite are tools that can execute test plan files and produce results in specified XML format
Test Reporting
- The results can be published at qa-reports.meego.com either manually or automatically
- The report shows the results for each test case and for each feature or bug
Automated Testing
Source file: Test_Management_overview.odp