Views
Quality/QA-tools
(→Tools and other utilities) |
(→Tools and other utilities) |
||
| (11 intermediate revisions not shown) | |||
| Line 33: | Line 33: | ||
|'''Tool (link to wiki page)''' ||'''Short description''' | |'''Tool (link to wiki page)''' ||'''Short description''' | ||
|- | |- | ||
| - | | Crash Reporter || On-device | + | | [[Quality/QA-tools/CrashReporter|Crash Reporter]] || On-device graphical front-end for sending core dumps produced by rich-core to core dump data base |
|- | |- | ||
| [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system | | [[Quality/QA-tools/OTS|OTS - open testing system]] || Test automation system | ||
| Line 47: | Line 47: | ||
| [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance | | [[Quality/QA-tools/QADashboard|QA Dashboard]] || Quality at a glance | ||
|- | |- | ||
| - | | Application Monitor || Monitor runtime indicators - CPU, memory, power for specified apps | + | | [[Application Monitor]] || Monitor runtime indicators - CPU, memory, power for specified apps |
|- | |- | ||
| - | | Video performance || Collect FPS, CPU information when do video playback | + | | [[System Monitor]] || Tool to monitor whole system status. |
| + | |- | ||
| + | | [[Power Diablo]] || Comprehensive and configurable power-sensitive workload. | ||
| + | |- | ||
| + | | [[Video performance]] || Collect FPS, CPU information when do video playback | ||
| + | |- | ||
| + | | [[TimedLaunch]] || Precisely collect application launch time automatically | ||
|- | |- | ||
| [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || Test cases and Cucumber steps for MeeGo QML UI applications | | [[Quality/QA-tools/QmlUITestlib|MeeGo QML GUI Testlib]] || Test cases and Cucumber steps for MeeGo QML UI applications | ||
| + | |- | ||
| + | | [[Testkit_Howto|testkit-lite]] || python based test framework, command line tool, supporting test definition xml | ||
| + | |- | ||
| + | | [[Testkit_Howto|testkit-manager]] || web based test tool with fancy UI, supporting both manual and auto testing remotely | ||
|} | |} | ||
| Line 76: | Line 86: | ||
| Service OS based Flasher || Flasher to support Intel netbook/tablet | | Service OS based Flasher || Flasher to support Intel netbook/tablet | ||
|- | |- | ||
| - | | Environment collector || Collect detail system environment information | + | | [[Environment collector]] || Collect detail system environment information |
| + | |- | ||
| + | | [[Memory eater]] || A small memory tool to measure system memory by eat memory Mb by Mb till swap happen | ||
| + | |- | ||
| + | | [[CleanPowerCycle]] || Repeatedly reboot device with specified times and wait time | ||
|- | |- | ||
| [[Quality/QA-tools/Corelysis|Corelysis]] || A daemon to process rich core dumps in the back-end server | | [[Quality/QA-tools/Corelysis|Corelysis]] || A daemon to process rich core dumps in the back-end server | ||
| Line 100: | Line 114: | ||
| [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || | | [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || | ||
|- | |- | ||
| - | + | | Qpid C wrapper library - libcqpid || | |
|} | |} | ||
| Line 129: | Line 143: | ||
* Relieve localization testing effort by automating all or part of it ([[Quality/QA-tools/Automation of L10n testing|Detail]]). | * Relieve localization testing effort by automating all or part of it ([[Quality/QA-tools/Automation of L10n testing|Detail]]). | ||
| + | |||
| + | * We may consider the need to have a fully functional test cases management system that could be widely used by the community to create/update test cases ([[Quality/QA-tools/TCMS|Detail]]). | ||
<BR> | <BR> | ||
[[Category:QA]] | [[Category:QA]] | ||
Latest revision as of 23:13, 16 January 2012
Contents |
Quality assurance (QA) tools
We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there.
Quality Assurance tools are developed to ensure MeeGo SW quality. QA tools team develops and maintains tools for quality assurance.
- "Open source tools – available for all, available for development and contributions. Make people accountable for quality."
Please note that developer-oriented content has been moved to QA tools development page. We apologize for any inconvenience. The target is to make this page clearer and more informative for the actual users of QA tools.
Overview
QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the figure below. In addition, there are also a couple of concept videos available at our YouTube channel:
Tools and other utilities
If you want to contribute to the development of the following tools, test suites and utilities, please visit QA tools development page.
Test tools
Each wiki page will contain more detailed description, installation instructions and tutorial on the basic usage. For now, please contact us if you need help. Currently, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, Meego-ai, libcqpid, eat and MIN from Tools:Testing repository. The instructions for setting up the repositories can be found here.
| Tool (link to wiki page) | Short description |
| Crash Reporter | On-device graphical front-end for sending core dumps produced by rich-core to core dump data base |
| OTS - open testing system | Test automation system |
| testrunner-lite | Command line tool for test execution |
| Testability Driver | Comprehensive tool for UI testing |
| QA Reports | Reporting tool for publishing test reports |
| Crash Reports Web UI | Web UI for Crash Reports |
| QA Dashboard | Quality at a glance |
| Application Monitor | Monitor runtime indicators - CPU, memory, power for specified apps |
| System Monitor | Tool to monitor whole system status. |
| Power Diablo | Comprehensive and configurable power-sensitive workload. |
| Video performance | Collect FPS, CPU information when do video playback |
| TimedLaunch | Precisely collect application launch time automatically |
| MeeGo QML GUI Testlib | Test cases and Cucumber steps for MeeGo QML UI applications |
| testkit-lite | python based test framework, command line tool, supporting test definition xml |
| testkit-manager | web based test tool with fancy UI, supporting both manual and auto testing remotely |
Other utilities
| Name (link to wiki page) | Short description |
| test-definition | XML schema for test plan and result files |
| eat - enables automated testing | Test automation configuration packages |
| MeeGo Automated installer | |
| Rich core dumper (sp-rich-core) | A tool to collect core dump and context data from process crashes |
| Crash Reporter settings | Settings package for Crash Reporter |
| Hardware Accessory for Testing (HAT) | |
| Scripts and utils | |
| Service OS based Flasher | Flasher to support Intel netbook/tablet |
| Environment collector | Collect detail system environment information |
| Memory eater | A small memory tool to measure system memory by eat memory Mb by Mb till swap happen |
| CleanPowerCycle | Repeatedly reboot device with specified times and wait time |
| Corelysis | A daemon to process rich core dumps in the back-end server |
Tools and utils not in active development
Tools listed here are in maintenance and no new features are planned to be implemented in the near future to them.
| Tool (link to wiki page) | Short description |
| Testrunner | Test execution tool with graphical UI |
| Testplanner | Simple tool for creating and editing test plan files |
| MeeGo Fast Feedback Testing (MeeGo-FFT) | |
| MIN Test Framework | Advanced test framework |
| Model-Based Testing adapter for qtuitest | |
| Qpid C wrapper library - libcqpid |
Feature requests and bugs
Want to report an feature idea or bug to us? - Please do it here
Bugzilla instructions:
Collaboration spaces
Team communication is in English. Our collaboration spaces are:
- meego-qa@lists.meego.com mailing list
- #meego-qa IRC channel on irc.freenode.net
- YouTube channel for demo videos
- QA-tools team blog
Nice to have
None of the existing tools answer your needs? Here is where you should enter any suggestion.
- Relieve localization testing effort by automating all or part of it (Detail).
- We may consider the need to have a fully functional test cases management system that could be widely used by the community to create/update test cases (Detail).