Views
Quality/Test management overview
From MeeGo wiki
< Quality(Difference between revisions)
m |
m (→Automated testing) |
||
| (2 intermediate revisions not shown) | |||
| Line 7: | Line 7: | ||
The figure below illustrates the process. The process is explained in more detail after the figure. | The figure below illustrates the process. The process is explained in more detail after the figure. | ||
| - | [[File:Test_management_manual_semi.png| | + | [[File:Test_management_manual_semi.png|810px]] |
'''Test planning''' | '''Test planning''' | ||
| Line 15: | Line 15: | ||
* The created test plans are avalaible at Gitorious repositories | * 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/] | ** 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 | + | ** Since Gitorious is a version control system, the plans can be used and edited by several users |
* The decision on which tests are to be executed is done in weekly test management meetings | * The decision on which tests are to be executed is done in weekly test management meetings | ||
'''Test execution''' | '''Test execution''' | ||
| + | * The testing is done by using agreed MeeGo release | ||
* The tests can be executed by several test engineers by using different execution tools | * 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]] | ** Testing can be done manually or by using automated testing environment [[Quality/QA-tools/OTS|OTS]] | ||
| - | * | + | ** [[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] |
| - | * [[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''' | '''Test reporting''' | ||
| Line 42: | Line 42: | ||
<br /> | <br /> | ||
| - | Source file of the figures: [[ | + | Source file of the figures: [[File:Test_Management_overview.odp|Test_Management_overview.odp]] |
Latest revision as of 16:56, 8 January 2011
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
- The decision on which tests are to be executed is done in weekly test management meetings
Test execution
- The testing is done by using agreed MeeGo release
- 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
- 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
The work flow in a nut shell with fully automated testing goes like this
- BOSS creates test automation enabled images from OBS projects (This part is not working yet. Currently OTS uses self made images.)
- OTS downloads the image and installs it to a device under test
- OTS executes tests found in the image
- OTS sends results to qa-reports.meego.com
Source file of the figures: File:Test Management overview.odp