Revision as of 10:57, 10 November 2010 (view source) Asinnela (Talk | contribs) (→Testrunner UI) ← Older edit		Revision as of 10:58, 10 November 2010 (view source) Asinnela (Talk | contribs) m Newer edit →
Line 33:		Line 33:
	## Modify comments of manual cases		## Modify comments of manual cases
	# Save the results.		# Save the results.
-
-	== Support and Links ==
-
-	There is a video, which demonstrates the basic functionality of an early version (v0.1), see [http://www.youtube.com/watch?v=-MBOiVb-2Z4 YouTube], and another video, which shows new features in version 0.2.5, see [http://www.youtube.com/watch?v=nileVzw52xM YouTube].
-
-	Upcoming features can be tracked in [http://bugs.meego.com/buglist.cgi?classification=MeeGo%20Platform&query_format=advanced&bug_status=NEW&bug_status=NEEDINFO&bug_status=ASSIGNED&bug_status=WAITING%20FOR%20UPSTREAM&bug_status=REOPENED&component=testrunner%20UI&product=Development%20Tools MeeGo Bugzilla].

---

Revision as of 10:58, 10 November 2010

Testrunner UI

Testrunner UI is a simple graphical user interface for testrunner-lite. It can be used for running automatic, semi-automatic and manual test cases. It takes a test plan file as input, runs the selected test cases and produces results in defined xml format. Testrunner UI can also be used together with Testplanner which provides a graphical UI for creating and editing the test plan files.

Testrunner UI is developed by QA tools team. You can contact us and contribute via the following channels:

• meego-qa@lists.meego.com mailing list
• #meego-qa-tools IRC channel on irc.freenode.net
• File new bugs or improvement ideas to Bugzilla
• Leave a comment or vote the items in our backlog
• Source codes in Gitorious

In addition, you can check our demo videos at Youtube:

• MeeGo QA tools Youtube channel

Installation

Basic Usage

The basic workflow goes as follows:

1. Open a test definition.
2. Select the test cases for execution. By default, all cases are selected.
3. Drag and drop test suites, sets, and cases to change the execution order.
4. Optionally enter results for manual cases and steps prior to test execution.
5. Run selected or all tests and see execution progress online.
   1. When prompted, enter results and comments for manual cases and steps.
6. After execution, view execution results in detail.
   1. See testrunner-lite output in a log view.
   2. See test case and step results and stdout/stderr output in a case detail view
   3. Modify comments of manual cases
7. Save the results.