Quick Guide to Mercury Quality Center / Test Director

Comments

This document contains screen shots and short comments on the basic routines in Quality Center v8 (powered by TestDirector). For a full manual, please refer to the “Help” function available from the sign-on screen in Quality Center.

1(32)

Table of Contents
1 Create Requirements..................................................................................................3
1.1 1.2 1.3 1.4 Create Requirement.......................................................................................................3 Create Child Requirement..............................................................................................3 Create Test Case Folder Structure from Requirement...................................................4 Viewing Execution Status per Requirement...................................................................4

2 Create Tests Cases in Test Plan.................................................................................5
2.1 Create Folder.................................................................................................................5 2.2 Create Test Case...........................................................................................................5 2.3 Create Steps..................................................................................................................7

3 Connecting Test Cases to Requirement......................................................................8
3.1 Connecting Requirements to a Test Case (from Test Plan)...........................................8 3.2 Connecting Test Cases to a Requirement (from Requirements)....................................9

4 Running Tests in Test Lab........................................................................................11
4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 Create Test Set Folders...............................................................................................11 Create Test Set............................................................................................................12 Set attributes on the Test Set.......................................................................................12 Select Test Cases to be run from Test Plan.................................................................13 Select Test Cases to be run by Requirement coverage...............................................13 Run Test Case.............................................................................................................14 Continue Manual Run..................................................................................................16 Update Test Plan.........................................................................................................17

5 Overview and Follow-up in Test Lab.........................................................................18
5.1 5.2 5.3 5.4 Selecting Columns.......................................................................................................18 Viewing test run details................................................................................................21 Graphs.........................................................................................................................22 Saving test result overview to Excel.............................................................................23

6 Printing stuff..............................................................................................................24
6.1 6.2 6.3 6.4 6.5 Print one test case in Test Plan...................................................................................24 Mailing a test case.......................................................................................................25 Print lots of test cases in Test Plan..............................................................................25 Printing test overview in Test Lab – quick and dirty.....................................................25 Printing lots of stuff – The Document Generator..........................................................26

7 General Tips.............................................................................................................27
7.1 7.2 7.3 7.4 7.5 7.6 Refresh !......................................................................................................................27 Grid view in the Test Plan............................................................................................28 Changing Password and Full Name.............................................................................28 Attaching Screen Dumps.............................................................................................29 Enabling Export from Word and Excel.........................................................................29 Exporting from Excel....................................................................................................31
2(32)

1

Create Requirements
1.1 Create Requirement

1.2

Create Child Requirement

1.3

Create Test Case Folder Structure from Requirement

Under Tools you find option “Convert to tests”. This option allows you to generate test case “skeleton” based on the requirements.

1.4

Viewing Execution Status per Requirement

When the test cases are connected to the requirements, the execution status per requirement is easily visible in the Coverage Analysis view in the Requirements tab.

2

Create Tests Cases in Test Plan
2.1 Create Folder

The easiest way to get the folders in a structured sorting order is to start the name with digits or equal. In the grid view in Test Plan and once the tests are included in a test set in Test Lab, only the lowest folder name is available, so keep the denotation to the lowest level (as in the above example). Remember that the folder structure is only used when maintaining test cases and not for follow up. 2.2 Create Test Case

Also for test cases, start the name with digits for easy sorting.

And remember that in the simplest kind of test reports, you will see the test case name and status “Fail” or “Passed”. Think of this when you decide on test case name: Will the test case name and the status supply proper information? Next, all attributes for the test case should be filled in. These are used for follow up, filtering, sorting etc and are important tags of the test case to classify it in several dimensions. For details around the attributes, please refer to the Test Director Tagging Guidelines and Rules around Customized fields. These documents are available in the Test Coordination db. Also the overall Description should be entered and the appropriate Status set.

2.3

Create Steps

Create test steps on the Design Steps-tab by pressing the icon “New Step”. The step name can be left untouched (just called “Step 1”, “Step 2” etc). The description should be on a level that makes it possible for the person who will run the test to know what to do. Depending on what the test case is intended for (advance process acceptance testing or detailed test that will be automated in the future), the level of detail of each step description can vary. Expected result should describe what to check when deciding whether the test step is passed or failed. Once the Design Step Editor is open, additional steps can be added with the “New Step”-icon in the editor window.

3

Connecting Test Cases to Requirement
If using the requirements functionality, test cases should be connected to each requirement on different levels. This can either be done from the Test Plan or from the Requirements tab.

3.1

Connecting Requirements to a Test Case (from Test Plan)

Select a specific test case and go to the Reqs Coverage-tab of that test case. Press “Select Req” to open a window to the available requirements.

Mark the requirement to connect the test case to and press the arrow “Add to Coverage….”. NB! There are two options in the drop-down on the arrow. • Include children – the test case is added to the coverage both of the requirement you have marked and to all its children. Without Children – the test case is added to the coverage of the marked requirement only.

3.2

Connecting Test Cases to a Requirement (from Requirements)

In the Requirements Tab, work with the “Coverage view”, mark a requirement and press select test.

Select a complete folder or separate test cases and press the arrow “Add to Coverage”

Mark requirement as Completely Covered As a confirmation that the requirement is fully covered by test cases, tick the box “Full Coverage”.

4

Running Tests in Test Lab
4.1 Create Test Set Folders

Create folders to organize test sets in groups. Remember that if any cross test set follow-up is required, the test sets must be marked with attributes. The folder structure cannot be used for summary reports! Folders is used only for the folder view in the Test Lab.

4.2

Create Test Set

A test set should contain all test cases to be run in one test session. If test results are split up on several test sets, the summary has to be created manually in the follow-up (or selecting several test sets with a filter). Name the test set beginning with a test session ID (decided by project manager or maintenance coordinator) or equal common notation. If a cross test set report is to be created over several test sets in the Test Lab, filtering on the Test Set name is an easy way to find the appropriate test sets.

Think: “One test report = One test set” 4.3 Set attributes on the Test Set

4.4

Select Test Cases to be run from Test Plan

Mark the folder, or individual test case that should be included in the test set and press the blue arrow (Add Tests to Test set). When selecting tests you can also use the filter function on the test case attributes to find the appropriate test cases. (for instance: all test cases for application FAS)

If the you filter only FAS test cases you can then mark and include all folders in the tree view, only FAS test cases will be included in the test set.

4.5

Select Test Cases to be run by Requirement coverage

Another way of selecting test cases to a test set is by using the coverage view.

By using this view, you can select all test cases connected to a specific requirement.

4.6

Run Test Case

Mark the test case you want to run and press “Run”. The test run is then stamped with date, time and tester. Press “Begin Run”. This is the point when the test case (as it looks at that moment in Test Plan) is copied to the Test Lab.

You can keep this window on top by pressing the “Keep On Top” icon. Press “Compact view” (the second circled icon above) to get a smaller window showing one step at a time.

Press Passed or Fail on each step to report the results. Remember: Actual result must be filled in on all steps that fail. If everything is OK, you don’t have to write anything. Then it is assumed that the expected result is true. When you reached and reported the last step, press the “double document-icon” ‘Back to Steps Grid’. Then press the red “dot” icon for “End of run” to return to the test set grid. You can also press the X and answer “yes” on the question about saving the run.

4.7

Continue Manual Run

To continue a run that has status “Not completed” in the overview, or to go back and add information on a finished test run, use “Continue Manual Run”. It is found under the Execution drop-down menu.

4.8

Update Test Plan

If anything is changed on the test case during the run, a question will pop up. If you answer “Yes”, the changes will update the original test case in Test Plan. This could be changes to the step description or expected result or if you have added more steps during the test run. NB! This means that new steps and improvements can be added to a test case while running the test.

5 Overview and Follow-up in Test Lab
5.1 Selecting Columns

To find the test cases in a big test set, you MUST select proper columns to be displayed in the Test Lab.

Sorting

Also the sorting is important to find your way around in the Test Lab. Press the “Filter and Sort” icon and select proper sorting. Detailed instruction is available on Using Grid Filter to find things….

You can create filters in the test lab to create selections to narrow down the amount of data displayed. The example above shows how to filter so that only the “problems” are displayed (Fail, Not Completed, etc … i.e. Not Passed) If you don’t see the grid filter fields at the top of the list, go to the drop-down menu “Tests” and tick “Grid Filters”.

5.2

Viewing test run details

Double click on a test case in the Execution Grid (in Test Lab) to see the detailed results for each test run. It is not possible to edit the results from here. To do that, you must select “Steps” or “Continue Manual Run”. (icons at the top right).

5.3

Graphs

To see a graph of your test set, go to the drop-down menu Analysis / Graphs / ‘Summary Current Test set’ or ‘Summary – Cross Test set’ (for graphs covering several test sets)

You can for instance select “Test Set” as the item for the X-Axis and group by “Status” (or any attribute field). Remember to use the filter function also here, if you want to view a graph on only a selection of the included test cases. Press Refresh to update the graph when you changed any settings. And if you double click on the legend you can pick what colors you want.  Note the icon for Copy to clipboard. And the possibility to save settings as Favorites (star-icons at top left).

and the tab for Data Grid… And use the Back-button to return to the Test Lab.

5.4

Saving test result overview to Excel

Ensure that you have the desired selection in the grid view (by setting a filter). Right click in the grid area and select Save As / Excel Sheet… You will be asked to name the excel sheet and where to save it.

6

Printing stuff
6.1 Print one test case in Test Plan

If you right click in the test step area, you can select “Save as…” “Word document”. Then you get a table like this: Attachment Step Name 100.100 Enter Customer Order Header 100.200 CO Line Entry 100.300 Customer Order Order Totals Check Description Co Header Entry Expected Result CO Header entered ready for Line Entry Customer Order Lines Entered All relevent Order Totals correct

Enter Customer Order Line Order Totals shown as per OIS110

You can also save as excel…. It’s a matter of taste….

6.2

Mailing a test case

User name works if the mail address has been entered on user properties. Otherwise, write mail address. This gives you all the details in a colourful mail.

6.3

Print lots of test cases in Test Plan

There are loads of options under Analysis. If you change the view in Test Plan to “Test Grid”, you can make some creative filters and then get the document of your choice.

6.4

Printing test overview in Test Lab – quick and dirty

FIRST! Make sure that the columns you need are available in the view. Right click in the test grid of all test sets you want and save as Excel /copy all data to one sheet.

Knock yourself out with pivot-tables, filters, summaries etc in the Excel-sheet.

6.5

Printing lots of stuff – The Document Generator

Under the Tools drop-down menu, you find Document Generator. This will produce lots of details in looooong word documents. Remember to sort your selection.

7 General Tips
7.1 Refresh !

Remember to use the Refresh button in TD to refresh the screen. If you use the internet explorer refresh, the whole TD window is refreshed and you’re back on the sign on screen….

7.2

Grid view in the Test Plan

When searching for test cases in the Test Plan, the grid view is useful. Then you can use filter and sorting on all attributes to find the test case. To locate the test case in the Test Plan Tree, mark the test case and press the icon for Find Test. (and look, there’s a Star-icon for managing Favorites)

7.3

Changing Password and Full Name

All users can change their password from the Tools drop-down menu in TestDirector. Below ‘Change Password’ you find the option Change User Properties, where each user can enter their full name (and the mail address you want TD to use). All users must have their full name in TD.

7.4

Attaching Screen Dumps

In most places in TestDirector, you can attach files or URL links. To attach a file, just use the paper clip-icon on the Attachment tab. To attach a screen dump, click the camera icon. You will then get a window looking like this:

This will easily capture a screen dump of the window you select. 7.5 Enabling Export from Word and Excel

If you have test cases or requirements documented in Excel or Word, these can be exported to TestDirector. From Excel the export is done by mapping each column to a field in TD.

From Word, you have to go through the document and mark each section as being a Test Case name, Step name, Description, Expected Result etc with special ‘markings’ that the TD/Word plug-in makes available in your MS Word. If you can choose whether the material is done in Word or Excel, the Excel export is more straightforward than the Word one. The Excel export also requires less preparation time for large numbers of test cases/requirements. You find the plug-ins and user guides from the Quality Center homepage

Select the “More Mercury Quality Center Add-ins”

Click the desired add-in to find installation instructions, software download and user guides.

7.6

Exporting from Excel

There is a template for a recommended layout of test cases in Excel in the Test Coordination db When you have the plug-in installed, mark the lines in Excel you want to export and go to Tools and you find the option ‘Export to QC’.

You give the address to Quality Center as below:

For more details around export from Excel (and Word), please refer to the user guides available along with the add-ins.

Sign up to vote on this title
UsefulNot useful