Manage manual test plans

Description

Generic Application for running and viewing a Manual Test Plan. It simplifies the burden of Manual Testing by allowing to fill in a TestCaseReport much more faster than traditional ways.
This is made for testing teams which want to run their TestCases inside XWiki.

Application features:

• Application offers more visibility over what has been tested than using traditional spreadsheets
• Browser and version a test was ran upon
• Database and version a test was ran upon
• Person who performed the test
• Capability to easily add or remove browsers with versions
• Capability to easily add or remove databases with version
• Capability to easily add or remove tests
• Offer visibility over the test phase
• Parallel users testing a Manual Test Cases
• Encourage the community to test more

Usage

The aplication was architectured so absolutely each test will have its own wiki page. On each page, XWiki Objects are added which specify a manual test execution.

• User logs in and goes to the QA.WebHome page. This is the main entry poing in the application
• In the LiveTable shown, user will see a list of tests and some additional information about the last product version which the test has been run upon
• You are also able to mark tests as being run
  
• From the Management console you can specify new browsers, databases with the desired version
• LiveTable images are provided by default for:
  • Browsers: Mozilla Firefox, Google Chrome, Internet Explorer
  • Databases: HypreSQL, MySQL, PostgreSQL, Oracle, IBM DB2, Apache Derby, Microsoft SQL 

Run a new Test

You can "mark" a test that you have ran on your machine directly from the LiveTable. There is a "Run Test" button from the livetable which will invoke a modal pop-up

Administration

There is the application Administration page which will allow you to add the Platform, Browsers, Databases which you are testing on, so you can have them as an option available for all your tests.

Technical Specifications

• QA.TestClass [attached to each page containing a test. Attached object to a page will mark that page as being a test. The test name will be the wiki page name and the steps to perform the test will be stored in the document content]
  •   description (TextArea) - Tells what the test is about e.g: "Tests that images are uploaded fine after a preview."

• QA.ExecutionClass (this will contain all information about a test execution)
  • test (DBList) - linked to QA.TestClass
  • product (DBList) - linked to QA.ProductClass
  • browser (DBList)  - linked to QA.BrowserClass
  • database (DBLIst) - linked to QA.PlatformClass
  • passed (Boolean)  - value to indicate if the test has passed or failed. Absence of an object for a specific platform/browser means not tested
  • jira (String)     - link to JIRA issue (if any)
  • tester (User)     - user that performed the test
  • date (Date)       - date when test was executed

• QA.PlatformClass (this will contain the version of XE that have been tested/currently being tested)
  •   name (String)     XE
  •   version (String)  4.1.2

• QA.ProductClass (this will contain the product version being tested)
  • name (String) XWiki
  • version (String) 5.2

• QA.BrowserClass (this will contain the browser versions that we support)
  •   name (String)     Mozilla Firefox
  •   version (String)  13

• QA.DatabaseClass (this will contain the database version that we support)
  • name (String) MySQL
  • version (String) 5.6

Prerequisites & Installation Instructions

We recommend using the Extension Manager to install this extension (Make sure that the text "Installable with the Extension Manager" is displayed at the top right location on this page to know if this extension can be installed with the Extension Manager). Note that installing Extensions when being offline is currently not supported and you'd need to use some complex manual method.

You can also use the following manual method, which is useful if this extension cannot be installed with the Extension Manager or if you're using an old version of XWiki that doesn't have the Extension Manager:

1. Log in the wiki with a user having Administration rights
2. Go to the Administration page and select the Import category
3. Follow the on-screen instructions to upload the downloaded XAR
4. Click on the uploaded XAR and follow the instructions
5. You'll also need to install all dependent Extensions that are not already installed in your wiki

Release Notes

v2.8

v2.7

v2.6

v2.5

v2.4

v2.3

v2.2

v2.1

v2.0

Changes since version 1:

• Model change. Now, each ExecutionClass object stores in the "test" property a reference to the Test it is pointing to.
• Decoupling between Tests and Executions. The Executions are not stored on the Test Page anymore. Instead, they are stored in pages located in the TestReportingExecutions space.
  • For example, a test called testAddAnnotations which is run on any 5.x version, the ExecutionClass objects will be stored in a page called "Annotations Tests.testAddAnnotations5". The rule on which this page name is generated is the following: testSpace.test + major product version.
• Custom LiveTables for Main page, Product Page and Test Page.
• Lots of other improvements

v1.0

• First implementation. The Test Executions are saved on the Test Page.

Dependencies

Dependencies for this extension (org.xwiki.contrib:application-testreporting 2.8.1):

• org.xwiki.platform:xwiki-platform-livetable-ui 12.10
• org.xwiki.platform:xwiki-platform-sheet-ui 12.10
• org.xwiki.platform:xwiki-platform-uiextension-ui 12.10