The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Quality
From Mer Wiki
(Difference between revisions)
(→QA tools) |
(→ToDo) |
||
| Line 44: | Line 44: | ||
* Plan simple test set for chroot environment | * Plan simple test set for chroot environment | ||
* Setup test automation for chroot environment (OTS and testrunner-lite should work almost out of the box) | * Setup test automation for chroot environment (OTS and testrunner-lite should work almost out of the box) | ||
| − | * Test result reporting (QA-reports) | + | * Test result reporting (QA-reports, see task [https://bugs.merproject.org/show_bug.cgi?id=244 Mer-244]) |
* Integrade testing into updating and release process | * Integrade testing into updating and release process | ||
** Also for SDK releases? | ** Also for SDK releases? | ||
Revision as of 13:03, 27 March 2012
Contents |
Quality
Under development, contributions are welcome!
Releases
| Release | Mer Core | SDK |
|---|---|---|
| Pre release xx |
|
|
| Current release xx |
|
|
Processes and test plans
QA tools
Used and maintained Quality Assurance tools in Mer:
HowTo's
ToDo
- Plan simple test set for chroot environment
- Setup test automation for chroot environment (OTS and testrunner-lite should work almost out of the box)
- Test result reporting (QA-reports, see task Mer-244)
- Integrade testing into updating and release process
- Also for SDK releases?
- Test management
- Virtual image testing, maybe nemo images
Contact
- Mailing lists
- IRC: Channel #mer on irc.freenode.net
Meetings
No meetings yet.
