m (→Overview) |
(→Tools and other utilities) |
||
| (43 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
= Quality assurance (QA) tools = | = Quality assurance (QA) tools = | ||
| + | |||
| + | ''' We moved our discussion to #meego-qa IRC channel as of March 24th 2011. Please join us there. ''' | ||
[[File:Tool_meegon.png|400px]] | [[File:Tool_meegon.png|400px]] | ||
| Line 8: | Line 10: | ||
'''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|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. | '''Please note''' that developer-oriented content has been moved to [[Quality/QA tools development|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 == | == Overview == | ||
| - | QA tools support test planning, test execution and test reporting. The most important tool offering relating to this is illustrated in the | + | 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 [http://www.youtube.com/user/meegoqatools YouTube channel]: |
| + | * [http://www.youtube.com/watch?v=WdXBqGdLz8I Tool offering for manual testing] | ||
| + | * [http://youtu.be/Ry4MM-CX2b8 Test automation] | ||
[[File:Meego-qa-tools.png|600px]] | [[File:Meego-qa-tools.png|600px]] | ||
| - | |||
| - | == Tools | + | == Tools and other utilities == |
If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]]. | If you want to contribute to the development of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]]. | ||
| Line 29: | 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 | ||
| - | |||
| - | |||
|- | |- | ||
| [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution | | [[Quality/QA-tools/Testrunner-lite|testrunner-lite]] ||Command line tool for test execution | ||
| - | |||
| - | |||
|- | |- | ||
| [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing | | [[Quality/QA-tools/TDriver|Testability Driver]] || Comprehensive tool for UI testing | ||
|- | |- | ||
| [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports | | [[Quality/QA-tools/QAReports|QA Reports]] || Reporting tool for publishing test reports | ||
| - | | | + | |- |
| - | + | | [[Quality/QA-tools/CrashReports|Crash Reports Web UI]] || Web UI for Crash Reports | |
| - | + | |- | |
| - | + | | [[Quality/QA-tools/QADashboard|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 |
|- | |- | ||
| - | | [[Quality/ | + | | [[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 71: | Line 72: | ||
|[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files | |[[Quality/QA-tools/Test-definition|test-definition]]|| XML schema for test plan and result files | ||
|- | |- | ||
| - | | [[Quality/QA-tools/Eat|eat - enables automated testing]] || | + | | [[Quality/QA-tools/Eat|eat - enables automated testing]] || Test automation configuration packages |
|- | |- | ||
| [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] || | | [[Quality/QA-tools/Autotest-guide#Automatic_image_installations|MeeGo Automated installer]] || | ||
|- | |- | ||
| - | | [[Quality/QA-tools/ | + | | [[Quality/QA-tools/rich-core|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 | | Crash Reporter settings || Settings package for Crash Reporter | ||
| Line 85: | Line 84: | ||
| [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || | | [[Quality/QA-tools/Scripts_and_utils|Scripts and utils]] || | ||
|- | |- | ||
| - | | Service OS based Flasher || | + | | 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 | ||
|- | |- | ||
| - | | Qpid C wrapper library - libcqpid || | + | | [[Quality/QA-tools/Corelysis|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. | ||
| + | |||
| + | {| border="1" cellspacing="0" | ||
| + | |+ | ||
| + | |'''Tool (link to wiki page)''' ||'''Short description''' | ||
| + | |- | ||
| + | | [[Quality/QA-tools/Testrunner|Testrunner]] || Test execution tool with graphical UI | ||
| + | |- | ||
| + | | [[Quality/QA-tools/Testplanner|Testplanner]] || Simple tool for creating and editing test plan files | ||
| + | |- | ||
| + | | [[Quality/QA-tools/MeeGo_Fast_Feedback_Testing|MeeGo Fast Feedback Testing (MeeGo-FFT)]] || | ||
| + | |- | ||
| + | | [http://min.sf.net/ MIN Test Framework] || Advanced test framework | ||
| + | |- | ||
| + | | [[Quality/QA-tools/qtuitest-mbt-adapter|Model-Based Testing adapter for qtuitest]] || | ||
| + | |- | ||
| + | | Qpid C wrapper library - libcqpid || | ||
|} | |} | ||
== Feature requests and bugs == | == Feature requests and bugs == | ||
| + | |||
Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here] | Want to report an feature idea or bug to us? - [http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Quality%20Assurance Please do it here] | ||
| Line 96: | Line 124: | ||
* [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order] | * [http://bugs.meego.com/buglist.cgi?query_format=advanced&order=Importance&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&bug_status=RESOLVED&component=eat&component=Fast%20Feedback%20Testing&component=hat&component=libcqpid&component=meego-qa-reports&component=min&component=ots&component=TDriver&component=testdefinition&component=Testplanner&component=Testrunner&component=testrunner-lite&component=Others&classification=MeeGo%20Projects&product=MeeGo%20Quality%20Assurance All open features and bugs in priority order] | ||
| - | Bugzilla | + | Bugzilla instructions: |
| + | * [[Quality/How To Report Bugs|How to report bugs]] | ||
| + | * [[Quality/Bug Life Cycle and Handling|Bugzilla workflow]] | ||
| + | |||
== Collaboration spaces == | == Collaboration spaces == | ||
| Line 102: | Line 133: | ||
Team communication is in English. Our collaboration spaces are: | Team communication is in English. Our collaboration spaces are: | ||
* [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list] | * [http://lists.meego.com/listinfo/meego-qa meego-qa@lists.meego.com mailing list] | ||
| - | * [http://webchat.freenode.net/?channels=meego-qa | + | * [http://webchat.freenode.net/?channels=meego-qa #meego-qa IRC channel on irc.freenode.net] |
| - | + | ||
* [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos] | * [http://www.youtube.com/user/meegoqatools YouTube channel for demo videos] | ||
* [http://meegoqatools.wordpress.com/ QA-tools team blog] | * [http://meegoqatools.wordpress.com/ 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 ([[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> | ||
[[Category:QA]] | [[Category:QA]] | ||
Contents |
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.
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.
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:
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 |
Want to report an feature idea or bug to us? - Please do it here
Bugzilla instructions:
Team communication is in English. Our collaboration spaces are:
None of the existing tools answer your needs? Here is where you should enter any suggestion.