The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Search results
From Mer Wiki
Create the page "Quality/QA-tools/Testrunner" on this wiki!
Page title matches
- = Testrunner-lite = ...t] test result file which can be published to for example qa-reports. With testrunner-lite, you can13 KB (2,007 words) - 07:56, 20 July 2012
Page text matches
- = Quality = * [[Quality/Test coverage|Test coverage]]5 KB (603 words) - 12:38, 8 October 2012
- sudo zypper in testrunner-lite eat-host Add needed tests to the image, look from [[Quality/Test_coverage | here]]3 KB (516 words) - 07:34, 29 May 2013
- ...elopment of the following tools, test suites and utilities, please visit [[Quality/QA_tools_development|QA tools development page]]. ...y#Contact|contact us]] if you need help. Soon, you can install Testrunner, testrunner-lite, test-definition, Testplanner, OTS, eat and MIN from Tools:Testing rep2 KB (322 words) - 04:37, 5 June 2012
- The Core set contains set of tests that verify overall quality of the Mer Core release. It has tests for all architecture domains and API * QA Tools were OTS, testrunner-lite, tdriver3 KB (517 words) - 16:34, 6 May 2012
- 3. type: Information about the viewpoint of the tests (which quality aspect of the software they are testing, see DevelopmentTestArea in Agile T ...of the XML and the possible attributes/values are defined in the [[Quality/QA-tools/Test-definition|Test Definition XML schema]]. It’s important to validate14 KB (2,068 words) - 12:20, 16 December 2013
- = Testrunner-lite = ...t] test result file which can be published to for example qa-reports. With testrunner-lite, you can13 KB (2,007 words) - 07:56, 20 July 2012
- [[Quality/Development#Guidelines]] first part till '''OBS''' will be replaced with a [[Quality/Terminology#Test package]] text (which even says to use /usr/share/<package4 KB (713 words) - 12:19, 16 December 2013