There are 3 different Manual launchers delivered with XStudio.
Depending on your needs, you have to choose the one(s) you prefer.
By experience, 90% of the users prefer using the Tabular manual launcher.






Tabular manual launcher (tabular_manual.jar)

The tabular manual testing launcher is probably the easer and the more flexible launcher for manual testing.
When the test operator starts the campaign session, the launcher will just display a large scrollable window containing 3 columns:
  • all the test prerequisites and scopes
  • all the test case descriptions (either formatted text or the refined test case procedure tree)
  • a toolbar and a comment field for each test case


Here is a screenshot:





Configuration

The Tabular_manual.xml file allows pre-configuring the launcher with some default values:

Parameter Description
Timing > delay between testcases (ms) Default value is: 0
Kalistick integration (opt.):
- browser to be used (if relevant)

- chrome local user(necessary only with chrome)
Possible values: [None], C:/Program Files/Internet Explorer/iexplore.exe,
C:/Program Files (x86)/Mozilla Firefox/firefox.exe, C:/Users/PC_name/AppData/Local/Google/Chrome/Application/chrome.exe.
Default value is: false


The toolbar

For each test case (and in the order he prefers), the test operator will have to just press one of the buttons in the toolbar on the right-hand side of the test case:



Different possible results

  • Success
  • Failure
  • Relative (when the test is neither successful nor failed)
  • Not executed (even if a test case has been set with another result, the test operator can set back the result to not executed)



Each time the test operator indicates a result, it is immediately stored in the XStudio database so that the results are never lost (even if your PC is crashing).

Reset all test cases with status

You can reset the status of ALL the testcases in one shot (success, failure, relative or not_executed).
To do that, you just press on the buttons in the toolbar at the top on the left-hand side.



When you reset all test cases, a confirmation message displays in the pop up windows.
You have the possibility to clear all test cases comments by checking the checkbox "Clear comments"
.



Automatic submission of comments

While editing the comments, text coloring indicates that it's not commited yet.

Associate a bug to a failed test case

There is two ways to associate a bug to a failed test case:
  • Create a new bug
  • Link to an existing bug


The bug-related buttons are currently available only if you're using the integrated bug-tracking database.
If the test operator clicks on one of the bug-related buttons, it will set automatically the test case as failed.


View/Edit a bug

During the second run of session, on each test, the bugs linked are listed.

You can view the details and edit them. To do that:

  • Click on the bug
  • The pop up Bug edition windows displays
  • Edit the bug by changing name, description, steps to reproduce, priority,...
  • Click on the Submit button


List attachment linked to test/test case

During the session run, on each test/test case, the attachments linked are listed.
You can open it by clicking on:
IMPORTANT: A tabular manual campaign run on its own and as such cannot be paused or stopped remotely from XStudio.



When the test operator has completed the testing, he has just to click on the Submit on the bottom of the panel and the session will stop.



Manual launcher (manual.jar)

The manual testing launcher can be used as is to perform manual testing if your tests are currently not automated and consist in just following some procedures. The launcher will use the testplan as entered in the system to request the user to perform some manual tasks and to answer some questions.


Configuration

The manual.xml file allows pre-configuring the launcher with some default values:

Parameter Description
General > set testcase as failed as soon as one step fails If set to true, when one step fails in the testcase the complete testcase is set as failed and the remaining steps are skipped.

Default value is: false
Timing > delay between testcases (ms) Default value is: 0
Kalistick integration (opt.):
- browser to be used (if relevant)

- chrome local user(necessary only with chrome)
Possible values: [None], C:/Program Files/Internet Explorer/iexplore.exe,
C:/Program Files (x86)/Mozilla Firefox/firefox.exe, C:/Users/PC_name/AppData/Local/Google/Chrome/Application/chrome.exe.
Default value is: false


These values can be changed while creating the campaign session from XStudio.


Control Bar

The manual launcher includes a control bar allowing controlling the execution of the tests. The control bar includes the following buttons:
  • Go back to previous test
  • Go back to previous testcase
  • Restart current testcase
  • Pause current testcase
  • Resume current testcase
  • Go forward to next testcase
  • Go forward to next test


Timeout per test

While executing manual tests, the launcher provides instructions to the operator to execute actions (and do verifications). The tests are configurable so that some timing restrictions can be added. For instance, it is possible to give 10 minutes maximum for the operator to execute the actions/verifications (i.e. you need to test that a message appears on the screen of the SUT in less than 10 minutes; if the operator doesn't validate that he saw that message within the 10 minutes then the test is automatically set as failed).

If you want to set some specific timeouts to a test you just need to associate to this test one or several of the following attributes (with a value for the timeout):
  • timeout test description (ms): maximum delay to validate the test description
  • timeout test prerequisites (ms): maximum delay to validate the test prerequisites
  • timeout testcases execution (ms): maximum delay to execute any actions or verifications implied by the testcases in this test


When manually executed, each test will be applied with their specific timeout values.

Note also, that all these attributes are dynamic. This means that when creating the campaign session, you can overwrite any of these default values (on each test if necessary) to customize one campaign session execution:






Simple manual launcher (simple_manual.jar)

The simple manual testing launcher differs from the Manual testing launcher by the fact that it will not prompt the user for each step and check but instead will show the complete testcase procedure and will just ask the user for a result. The setup/configuration is exactly the same.

Configuration

The simple_manual.xml file allows pre-configuring the launcher with some default values:

Parameter Description
Timing > delay between testcases (ms) Default value is: 0
Kalistick integration (opt.):
- browser to be used (if relevant)

- chrome local user(necessary only with chrome)
Possible values: [None], C:/Program Files/Internet Explorer/iexplore.exe,
C:/Program Files (x86)/Mozilla Firefox/firefox.exe, C:/Users/PC_name/AppData/Local/Google/Chrome/Application/chrome.exe.
Default value is: false


These values can be changed while creating the campaign session from XStudio.




Some popup dialog boxes will ask the operator to execute some operations and/or verify some assertions