MMS TEST ENGINEERING

TRAINING
1

Test Plan
Main Toolbar in Test Plan
Icon is used to add new folders to the directory structure. Same task can be completed by going to Tests | New Folder. Icon is used to add a new test plan to the folders. Same task can be completed by going to Tests | New Test. This icon can not be used. To delete test plans refer to Deleting Entire Scripts section of this document. Icon used to refresh the screen. The same task can be completed by going to Versions | Refresh. Filter icon is typically not needed in this screen, but can be used to limit the data that you are viewing. This icon can be used to sort the folders in a different order. This is used to flag a specific CR with a flag, comment, and follow-up date. It will also send you an email with the follow up comments and a link to the test script. Option is not installed at this time.

Version Control
Version control was put in place on all scripts in Quality Center. In order to add, edit, or delete steps from a script, the script must be Checked Out. You may do so by going to the Versions menu or right clicking on the script and choosing Versions | Check Out. When checking out a script, add a brief description for the reason you are checking out the script to the comment field. If we need to revert to a previous version, it is easy to determine which version to go back to when the description has been added. To view the version history of a specific script go to Versions | Versions. This will list all of the versions, the user, and the date. Each line will show the comment that was entered to describe the reason for change.

You may check out a script from the screen or pull up a previous version of the script. You are unable to make changes to a previous version, but you can copy the previous version to create a new script. After you are done viewing the previous version you will need to go to Versions | Get Latest Version to revert your screen to the most updated version of the script. Be sure to check in your scripts when you are done. If you do not check them in, other people will not be able to see the final version, they will only be able to see the previously checked in version.

Creating a New Script

In test plan, highlight the folder you would like to add a new script to. If no folder exists you will need to create one by going to New Folder Icon or by selecting New Folder from the Tests menu option. Refer to H:\Support\MMS\MMS_Implementation\Procedures\Testing_Scripting\Guidelines for Scripts in Quality Center.doc for information on directory structure and naming conventions. Once the folder is created you can add a new script by clicking on the new test icon (shown above) or selecting New Test from the Tests menu option. After selecting a New Test you will see the Create New Test window. Enter the Test Name and click OK. Your test script is now created.

Tabs / Icons for Script Writing

Details tab The Details tab should be used to store information related to the script as outlined in the Guidelines for Scripts in Quality Center document. (H:\Support\MMS\MMS_Implementation\Procedures\Testing_Scripting\Guidelines for Scripts in Quality Center.doc) Design Steps tab Steps of script are added, edited, and deleted from this tab. This tab contains the Save button. It is recommended to save often. Test Script - The Test Script tab is used for automated testing with Quick Test Professional. MMS Automation uses Test Execute rather than Quick Test Professional. Attachments This tab can be used to store attachments for a script. Please note the attachments on this tab do not carry through to Test Lab when running the scripts. This tab can be used to store trainings or general information that is not required during the actual testing. Req Coverage Req Coverage is not used at this time. Linked Defects See Linking Defects to Tests in the Test Lab section of this training - This icon is used to add a step to the script. You may also use ALT+N on the keyboard to add steps. - This icon can be used to edit a step. You may also double click on a step to edit or place your cursor in the step and begin typing. - This icon is to renumber your script. Adding steps, deleting steps, or moving steps around may require you to renumber the steps. This button will do this automatically. - This icon is used to delete a step or series of steps. You may also use the delete key on your keyboard when the row is highlighted. - Can be used to copy a step. You may also highlight the step and CTRL+C. - Can be used to paste the step you have in your clipboard. You may also use CTRL+V. - Use this icon to add attachments to specific steps. The attachments associated with specific steps will carry over to the Test Lab area when running scripts. - This icon can be used to make a call to another script. It will create a link within the current script you are working on to the script you are calling. This can be useful when you want to reference both scripts while writing because it allows you to easily toggle between them. A downfall to using this feature is when executing the script that includes the call. All the steps will appear in the execution run of the script you are working on and the one being called. It can make for an incredibly long script. - Icons used mostly with automated testing with Quick Test Pro.

- Search icon can be used to search for a word or words within the script you are in. - Select Columns icon will allow you to modify the columns that display in the screen. - Adjust row height icon can be used to increase the row height on all rows in the script that are longer than what is currently displayed. You may also adjust the row height by using the double arrows that appear on the left hand side of the grid and stretch as you would in excel or a word table. - Save icon should be used often. You may also use CTRL+S to save your steps. Note: All of the above icons can also be found when right clicking in the Design Steps tab. The formatting options of Bold, Underline, Italics, and Font color only appear when you are editing the Description tab or editing steps of a script. The Formatting Toolbar will appear along the right hand of the screen when editing in the grid of the script or description tab. If you are in the Design Step Editor screen the options will show on the right side of that screen.

Adding and Inserting steps into a Script

Your steps are located on the Design Steps tab of your script. Add a step by clicking the New Step icon or ALT+N on the keyboard. Once the step has been added, the Design Step Editor window appears.

Note: The Design Step Editor screen contains some of the icons that the main screen has but in addition it has a Spell Check option and a Thesaurus option. You may also use the arrows in the screen to traverse through the different steps of the script.

You can add the contents of your test scenario in this screen OR you can click OK and the blank step will be created on the Design Steps tab and you can edit the content of the step in the grid of the script. If your preference is to work on the Design Step Editor screen, you can click the save icon located on that screen, instead of clicking OK, after you have completed your test scenario.

Once it is saved, you can select the New Step icon right from here and the screen will be blank for you to create your next step. Whether you are editing scripts from the grid display or within the Design Step Editor, you should save your changes often. SAVE SAVE SAVE! Inserting steps in between existing steps can be done in the same manner as adding new steps. You just need to highlight the step that you want before your newly inserted step. Once you create your new step, the Design Step Editor screen will appear and proceed as normal. Just keep in mind that you are only able to insert below an existing step so be conscious of the existing step you have highlighted when adding a new step.

Copying Steps
You may copy a step from within the script you are working in, or from previously created scripts. To do so, highlight the entire step or series of steps and copy. Within your current script, place your cursor above where you want the step(s) to be inserted and paste. This will place your copied steps above the step that you selected. You may also highlight the words within a step and copy them to another step. Be sure you have your cursor in the step, highlight the words and copy. Then go to the step you would like to copy into and paste.

Deleting Entire Scripts

If you need to remove a script from Quality Center you must have the script checked in to do so. After it has been checked in, you can then move it the folder labeled To Be Deleted MM/DD/YY. You can simply drag and drop the script you want to delete to this folder. Note: In order for the Quality Center admin group to delete the scripts moved to the To Be Deleted MM/DD/YY folder, the script must be checked in prior to moving it to the folder.

Copying Entire Scripts

If you would like to copy an entire script from one folder to another folder in the directory structure, highlight the script, copy and paste into the appropriate directory. This will put the new version of the script to version 1.1.1. If the name of the script already exists, it will add Copy_1 to the end of the name of the script. It will not automatically check the script out for you as it does when creating a brand new script.

Printing Scripts
Report printed directly from Quality Center

1. In Quality Center, select the Test Plan icon on the left hand side. 2. Highlight the script you want to print and click on Analysis | Report Selected. (OR, right click
on the script and select Report Selected.

3. Click on the Green Gear Icon

4. Right click on Planning Report. 5. Select Add Sub-Report | Design Steps.

6. After selecting Design Steps, check the radio button for All fields this will bring the REQ# field into the report. 7. At the bottom of the screen, click on Apply.

8. Once the report is on the screen, click on the printer icon and select the printer.

After it prints, click on Close to get back to the Test Plan view.

Emailing Script and Printing from Word 1. In Test Plan, highlight the script you would like to print. 2. Click the drop down on the envelope icon and select Send by E-mail (or right click on the
script and select Send by E-mail)

3. Enter your username in the To field (you do not have to put @paychex.com at the end) 4. Click Design Steps then click Send

This will send a copy of the script to your email. From there you can print directly from email or copy the contents into a word document, set the borders for the fields. This allows you to have the landscape format versus the portrait format as it is printed from Quality Center.

Report printed from Document Generator in Quality Center 1.

Close Microsoft Word. Document Generator sends the data to a word document. If word is open it will not work (will be really slow). 2. Note the exact name of the script you plan on printing. Exact spaces, underscores, etc are needed.

3. 4.

In Quality Center in the top right hand corner click Tools | Document Generator.

Within the Document Generator select public: Print Script MMS Test Engineering from the favorites drop down at the top center of the screen. 5. 6. 7. 8. 9. Click on the plus sign next to Test Plan to expand the tree. Click on the plus sign next to Subject Tree to expand this level. Click on Subject Tree (highlight it). Click the plus sign next to MMS Test Engineering. Continue clicking the plus signs until you see the folder that your script exists in.

10.

Click in the box next to the folder where your script resides. An X must be in the right folder for it to find the script and bring it to word.

11.
12.

Back on the left side of the screen, click on the words Subject Tests. On the right hand side of the screen, click the Filter & Sort button.

13.

To print one specific test script, click on the Test Name row. Enter in the test name. If the test name contains any blanks or spaces between words, then put quotation marks around it. (For example 567636_Arizona Table changes) 14. 15. 16. You can add other filters as needed. You can also set conditions on filters. When you are finished, click on OK. Click on Full Document button at the top of the window.

17. A window will pop up where you can name your output and select what directory to put it in. Enter a name and click on Save. The Document Generator will begin. 18. Once you access the Word document on your local drive, you can format it the way you want. For instance:

Delete the first page or two if necessary. Landscape the report. Change the width of the columns in the table to fill in the landscape page. Click on the top row of the table and click on Table | Heading Row Repeat.

Test Lab
- Use this icon to create a new folder within the directory structure. - This icon is to create new test sets. This can also be done by going to Tests | New Test Set or using ALT+N. - Can be used to delete Test Sets, however you should never delete a Test Set that has been executed and passed for a project or CR. This testing proof is necessary for auditing purposes.

10

Icons with Execution Grid - This button should be used to add more tests to an existing test set. - Two options exist within the drop down arrow of this button. You may choose Run Manually or Continue Manual Run. Just clicking the Run button will do the same as Run Manually. - This button could be used if you had multiple tests within a test set and you wanted to execute all of them in one session. - You may use this button to add columns to your grid. This is useful for adding the Defect Status information to the grid when linking defects to your test run. - Test instance properties icon shows you the detail run information for a particular test.

Creating New Test Sets

1. Highlight the folder (e.g., April) of the sprint or project you want to execute a test for. If it
doesnt already exist, you will need to create it by going to Test Set | New Folder. When creating the new folder, use the Test Plan directory structure as your guide. 2. Click on the Test Set Menu Option, then New Test Set

3. New Test Set window appears. Enter the Test Set Name.
System Tests - Use the CR number and a brief description of the CR as your Test Set Name. This may follow the same naming convention as the name of the script in Test Plan. At minimum, the Test Set Name needs to include the CR number. Regression Tests - Use the Sprint or Project name then the word regression (April_Regression, TOA_Regression) as your Test Set name.

4. Click OK when done Once the Test Set has been created, you will now need to select test(s) to be included in the Test Set. Quality Center sometimes automatically displays the Test Plan Tree when you have created a new test. If it does not appear on the right hand side of your screen, click on Select Tests button located on the top of the Execution Grid. Once you do that, the Test Plan Tree will appear on the right side of the Execution Grid. In the Test Plan Tree, locate the script(s) that you want to execute. Highlight it and move it to the Execution Grid.

11

The Test Plan Tree appears on the right hand side of the screen when adding a new test or clicking the Select Tests button. There are many options to actually add the test once the test is highlighted you may; Click the green arrow, Double click on the test, Right click and choose Add Tests to Test Set, CTRL+A. If you dont see the script that you need to execute, click on the refresh button located at the top of the Test Plan Tree. If that doesnt work its possible that the script has not been checked in by the script writer. The script MUST be checked in to be able to execute it in the Test Lab.

Adding Script to an Existing Test Set (Regression)

Multiple scripts will accumulate in the Regression Test Set. Anyone can add scripts to the Test Set at anytime.

1. Select the Regression test set you wish to add to. 2. Click the Select Tests button on the menu bar of the execution grid. 3. On the right side of the screen you will see the directory structure in the Test Plan Tree. 4. Select the script you wish to execute and add it to the Execution.
This will add the script you selected to the list of already existing test scripts within that test set. You can execute each script in that test set individually and while other users are executing different tests within that test set.

Running Test Sets

- You may add a step to the test you are executing with this button. It will add the step to the bottom of the test. You will need to enter the description and expected result at the bottom of the screen. It will not provide a separate window as it does in Test Plan. - You may highlight a step and use this button to delete. We currently do not have the rights to use this and can not be given them at this time. - This button allows you to pass the selected step or use the drop down arrow to pass all steps. If you need a status other than pass (or fail) you can change the status manually on the step.

12

- This button allows you to fail the selected step or use the drop down arrow to fail all steps. - Parameters field is used for testing with Quick Test Pro. - This button can be used to view the existing attachments or to add new attachments. - You may use this button to create a defect from the step you are executing. You may also use CTRL+B. You can find more information on this option in the Linking Defects to Tests section. - This button can be used to keep the Quality Center window on top of all other windows. - This button will allow you to have a very small box showing the Step, Description, Expected, and Actual. - You may change the filter in your test run to show only a certain status, like all steps with Not Run or Failed. - Use this button to end your run. Ending the run will save the status of your test. If you made changes to the description or expected results clicking on the End Run button will allow you to save your changes back to the script in Test Plan. Once the Test Set is complete, you can run the script manually. The preferred method to executing scripts is to run them in Quality Center as you are testing. This allows us to capture accurate testing information. You could be executing a single script within a test set or one of many tests within a test set. For both scenarios, follow the steps below: 1. Highlight the specific test in the execution grid (only click once).

2. Click on the Run button at the top of the execution grid. The Manual Runner screen will
appear.

3. Click the Begin Run button within the Manual Runner screen.
Another screen will appear displaying all of the steps from the script with the test case and the expected result. Each step should be updated with the appropriate status of Pass, Fail, Not Complete, or N/A. You may enter actual results in the Actual section of the screen. If you find that a description of the step or expected result of the step is incorrect you may update the script from the Test Lab. Make your changes on the step as you are testing, once you Stop the run, you will be prompted on if you want to save your changes back to the test plan.

13

Selecting No will keep your changes in the actual run but will not be available for anyone who uses that script in the future. Selecting Yes will ask you to check out the script. Your changes will go into the script back in Test Plan. Go to the Test Plan tab and check the changes back in. Once the test has been executed, regardless of pass/fail status, click on the End Run button when you are no longer able to continue because of Fail status, you have completed and passed all of the steps in the script, or you have to stop for the day. Based on the status of your steps, the overall status of the script will be indicated in the Execution Grid. Note: If you click Run/Begin Run on a script you did not intend to run. You may close the window and discard that session by using the Red X to exit the screen. Select No when prompted if you want to save the test run.

Executing Previously Started Tests

If a script is tested more than once (regardless of pass/fail status), it must be executed in Test Lab for each time it is run. In addition, if a step fails it should be captured within the test run. This allows us to accurately reflect how many times we had to execute a script before it passed.

If you need to stop testing for the day and need to pick it up again later
Double click the test to open the Test Instance Properties. Click the Continue button on the right side of the Test Instance Properties screen. Then click the Begin Run button. This will bring you right back to where you previously left off. The pass/fail status for the steps and actual results will still be there. When there is only one execution of the test you can click the drop down arrow from the Run button and select Continue Run. This doesnt work well when the script has been executed previously.

If you have failed a test and now have new code

Highlight the test and click the Run button on the Execution grid. In the next screen click Begin Run. This will bring you into a clean version of the test. No steps have pass/fail status or any actual results.

If you passed a test and now need to re-test based on new code turnover
Highlight the test and click the Run button on the Execution grid. In the next screen click Begin Run. This will bring you into a clean version of the test. No steps have pass/fail status or any actual results.

14

Note: For any of the above scenarios, avoid bringing script into execution grid again.

Viewing Detail of Test Runs

To see the history of this particular test you may click the Test Instance Properties button or double click on the test. The following screen will display

The Test Instance Properties displays all executions of a script. You can see the actual steps in the bottom left corner and the step details on the bottom right. Double clicking on the tests within this screen will show you the Run Steps in further detail. Do not double click to run the test. You must click Continue to do so.

Linking Defects to Tests

You can link a defect to the following entities: tests (test plan), test sets, test instances, runs and run steps. Defect linkage is useful, for example, when logging a defect from a run step, the contents of the step will automatically be input into the defect. A defect is linked directly or indirectly based on the location of where you log the defect. When you add a defect link to an entity, Quality Center adds a direct link to this entity and indirect links to other related entities. In addition, during a manual test run, if you add a defect, Quality Center automatically creates a linkage between the test run and the new defect.

15

For example, when you link a defect to a run step, Quality Center adds an indirect link to its run, test instance and test set. Note that the indirect linkage is a one-directional flow. For example, if you link a defect to a run it is not indirectly linked to its run steps. Using the Linked Defects dialog box or tab, you can view and manage defect links.

Viewing Linked Defects

You can filter links, set column appearance and order in the grid, and refresh the grid. In addition, you can view details of a defect and instruct Quality Center to go to a module and highlight a linked entity. - To refresh the grid, click the Refresh All button. - To filter and sort the defect links, click the Set Filter/Sort button. - To set column appearance and order in the grid, click the Select Columns button. - To view details of a defect, select a defect link and click the Defect Details button.
To open the Defects module and highlight the linked defect, select a defect link. Click the Go

To arrow and choose Go To Defect. Alternatively, click the Defect ID link to open the Defects module and highlight the linked defect.
To open the relevant module and highlight the linked entity, select a defect link. Click the Go

To arrow and choose Go To `Linked By' Entity. Alternatively, click the Linked Entity Name link to open the relevant module and highlight the linked entity. To display direct links, select Direct Links from the Type of Link list. To display direct and indirect links, select All Links. Not available in the Defects module.

Adding Defect Links

You can add a defect link by submitting a new defect or by selecting an existing defect.

16

Submitting a new defect:

In the Linked Defects tab or dialog box, click the Add and Link Defect button , or right-click the grid and choose Add and Link Defect. The New Defect dialog box opens. Enter the relevant defect details. For more information on adding defects, see the Entering New Defects section of this training. Click the Submit button in the New Defect dialog box. The defect is added to the project and the defect link is displayed in the Linked Defects grid.

Selecting an existing defect:

In the Linked Defects tab or dialog box, click the Link Existing Defect arrow the grid and choose Link Existing Defect. Choose By ID or Select: , or right-click

To add a link by typing a defect ID, choose By ID. In the Link Existing Defect dialog box, type the defect ID and click Link. The defect link is displayed in the grid. To add a link by a selecting a defect, choose Select. In the Defects to Link dialog box, select the defect. To select more than one defect, press the Ctrl key and select the defects you want to link. Click Link. The defect links are displayed in the grid.

Removing Defect Links

You can remove defect links from the Linked Defects grid. Note: You can only remove direct links. Indirect links are removed automatically when the direct links are removed. To remove a defect link:

In the Linked Defects tab or dialog box, select a link in the grid. To select more than one defect, press the Ctrl key and select the defects you want to remove. Click the Remove Link button Click Yes to confirm. , or right-click and choose Remove Link.

Execution Notification Report

Print the Execution Notification Report when testing has been completed and all steps have passed for a script.

17

Click on Analysis | Reports | Execution Notification Report. Depending on the number of records or the type of history you may need, use the Green Gear icon to alter the settings. To show additional detail records of all runs click the History option. Print the report and place it in the CR folder or designated location for a project.

Additional option: Right click on the executed test and select Report Selected. This option only works for single test executions, if you have multiple tests (ex. April_Regression) you will need to use the Execution Notification Report to show all tests (if necessary).

Defects
- This button will bring up the New Defect window. Within the Defects screen you may also use ALT+N. - Button is not used in this screen. - Use this button to set the Filter/Sort. Information on how to create filters can be found in the Filtering Defects section below. - You may add or remove columns from you display of issues. - This button will provide the details of the defect record you are on. You may also get the details of a record by double clicking on the record. - This button will allow you to email the details of the issue to a specific email address. Additional options exist with the drop down. - You button is to find similar defects or similar text within the defects section. It does not work very well. - Button is not used at this time.

18

Entering New Defects

All fields in red must be entered in order to submit the issue. Summary (Title) Enter a brief summary of the issue. Detected By and Detected on Date will be pre-populated when entering the screen. Assigned To Select the developer for the CR or project. Quarter Select the appropriate sprint or version. Phase of project Select System Testing when you have found the issue while doing System Testing. Select Regression Testing when you have found the issue in Regression Testing. Other options used by our group include Simulation Testing and Beta Testing. Platform Select Hub, Client, Hub and Client, or eServices Agent. Requirement Requirement number from the project (if applicable). (Not required)

19

CR Number This field is not required however it is very beneficial. (Not required) Project Select the appropriate project or MMS BAU from the list. If the project does not exist, you will need to submit a defect to the Quality Center admin group to have it added. Check with Development as they may have already submitted the request. Severity The severity of the issue. It can range from 1 to 5 with 1 being Urgent and 5 being Low. Below is the severity level definitions:

o 1Ugent (Showstopper) Defects that can be described as infectious, catastrophic, or intolerable. They include: System lockup, crash, or other problem that results in data loss or corruption. A failure to compete the application's major tasks or transactions and there is no work around A defect that compounds itself by affecting other modules, tasks or data Basic Functionality is not working (i.e. Add Agency, Add Worker, screen doesnt start up, function and/or save does not work). o 2Very High (Critical) Defects that can be described as extreme, or serious. They include: System lockup or crash that incurred no loss or corruption of data A failure to complete the application's major tasks or transactions and the work around cannot be used because it is time consuming, too difficult, or impossible to do A defect that is the result of missing a requirement that affects data and/or transactions, e.g., missing data field, wrong field protection or security Major business requirements not being met. The defect is contained within common code shared across multiple components. o 3 - High Defects which can be described as disturbing or annoying. They include: Any defect that impacts performance specifications in heavily used areas of the application, A problem that has a work around, but it is inconvenient to implement and use Any defect which affects data, transactions, or performance that occurs in more than one module or area of the application Incorrect default values in a field or incorrect prompts Enabling/Disabling fields based on business logic. o 4 - Medium Defects that can be described as moderate, or somewhat annoying. They include: Problems that have a work around that is simple and not time consuming for the Client, Any problem that results in a defect condition that is detected at the Branch level only, and has a work around. Not noticeable by the Client Erroneous navigation through the application Problems with Enabling/Disabling, Clear Changes/Save buttons. 20

o 5Low Defects that can be described as mild. They include: Documentation errors other than on-line help, Incorrect field attributes Incorrect GUI attributes Incomplete, non-intuitive, or incorrect on-line help text Look and Feel standards (i.e. number of pixels, rounded/square corners).
Sub Application This is the area of the issue. This has a range of options. Try to choose the option closest to your issue. Log Type This is used mostly for statistical reporting. Most of the issues reported by the testing group are Defect. Some other commonly used types are Duplicate, Enhancement, Environment, Escalated, Pre-existing, and Requirement. Development may change the log type to one of these statuses after they have verified the issue from Defect to Pre-existing. Description This should contain as much information as possible on the symptoms of the issue, detailed how to duplicate steps, and clients if applicable.

Additional fields that are used by MMS Test and MMS Dev: Status This field automatically set to New when entering a defect. It will be reassigned to the person who submitted the issue when development is complete. Testing will verify the issue is resolved and change the status to Closed. If the issue is not resolved update the status to Re-open and reassign the issue to the developer. Rejection Reason If the above Status field is set to Rejected, the Rejected Reason is required. This is also for statistical purposes. - Clear button will empty all of the data that you have entered in the screen. - Can be used to spell check your work in the New Defect screen. F7 will also launch spell check. - This button is used to set up your options for spell check. - Thesaurus for the New Defect screen. You may also use SHIFT+F7.

Updating Defects
Once development has addressed your issue, locate your defect in the Defects screen. You will need to update the defect with comments regarding the issue. You may open the detail of the defect by double clicking the issue or clicking the Defect Details button. Within the Defect Details screen you can update the Status and the Assigned To fields. To update the Description of the issue or add a comment to the defect, select the Description button on the left hand side.

21

On the bottom right hand side you will see Add Comment button. Click Add Comment to place your name and the date to the record. Begin typing right next to your entry.

You may also update the Status, Assigned To, Description, and Comments right from the grid of issues.

22

Flow of Defects
New issue is discovered by MMS Test Eng: 1. Issue is entered in Defects of Quality Center. Appropriate data is entered in all required
fields. The Status should be New by default and Assigned To should be updated to the developer username. 2. Developer verifies the issue and updates the Status to Open. If issue is not determined to be valid, go to section for Rejected Issues. 3. Developer finishes the development work. Development tool updates Status to Fixed and Assigned To updated to tester username. 4. Tester verifies the issue has been resolved. a. If issue has been resolved Tester enters comment with information and updates Status to Closed. b. If issue has NOT been resolved Tester enters comment with information on why it does not fix the issue, updates the Status to Reopen, and updates the Assigned To back to the developer username.

New help file issue is discovered by MMS Test Eng: 5. Issue is entered in Defects of Quality Center. Appropriate data is entered in all required
fields. The Status should be New by default and Assigned To should be updated to MMS_Support_Projects. The Sub Application field should be set to Help File. 6. Information Management verifies the issue and updates the Status to Open. The Assigned To field is updated from the group name to the username of the person working on the issue.

23

7. Information Management user finishes the change and updates Status to Fixed and
Assigned To updated to tester username and completes the turnover to Test Engineering task. 8. Tester verifies the issue has been resolved. a. If issue has been resolved Tester enters comment with information and updates Status to Closed. b. If issue has NOT been resolved Tester enters comment with information on why it does not fix the issue, updates the Status to Reopen, and updates the Assigned To back to MMS_Support_Projects.

Issue was not resolved with new code (continuing from 4b): 1. Status remains in Reopen status while developer works on the issue. 2. New code is completed by developer. Development tool updates the Status to Retest
and Assigned To updated to tester username. 3. Tester verifies the issue has been resolved. a. If issue has been resolved Tester enters comment with information and updates Status to Closed. b. If issue has NOT been resolved Tester enters comment with information on why it does not fix the issue, updates the Status to Reopen, and updates the Assigned To back to the developer username.

Rejected Issues:
When the issue is being verified by Development, they may find that the issue is not valid or pre-existing.

1. The Status of the issue will be updated to Rejected. The Assigned To will be updated to
the tester username.

2. Once an issue is put in the Rejected state, a Rejection Reason must be selected.
Possible Rejection Reasons: Duplicate, Enhancement, Help File, Not in requirements, Other, Pre-existing, Standards not defined, Too low of a priority, Unable to reproduce, Working as Intended. 3. The tester should verify the information provided by the developer. a. If the tester agrees with the developer - Enter a comment with any follow up information. The Status field should remain as Rejected and the Assigned To should remain as the tester username. b. If the tester does not agree with the developer Enter additional information in the comments to help the developer with the issue. Update the Status to Reopen and update Assigned To back to the developer username.

Issue Reporting by Simulation Testers 1. Issue is entered in Defects of Quality Center. Appropriate data is entered in all required
fields. The Status should be New by default and Assigned To should be updated to the OSS Lead. 2. The OSS Lead updates the Status to Open when they begin verifying the issue to show they are investigating. This could also be done by MMS Test Eng if the OSS Leads have a lot building up. 3. If issue is determined to be valid, the OSS Lead or Test Lead will move the Status to Issue Verified and the Assigned To updated to vcritten.

24

4. If issue is not determined to be valid the issue will be rejected. The issue can be rejected by the OSS Lead, MMS Test Eng, or Development. a. The Status of the issue will be updated to Rejected. The Assigned To will be updated to the SIM tester username. (this will be looked at during the next SIM event) b. Once an issue is put in the Rejected state, a Rejection Reason must be selected. Possible Rejection Reasons: Duplicate, Enhancement, Help File, Not in requirements, Other, Preexisting, Standards not defined, Too low of a priority, Unable to reproduce, Working as Intended. 5. The tester should verify the information provided by the developer. c. If the tester/OSS Lead agrees with the Rejection - Enter a comment with any follow up information. The Status field should remain as Rejected and the Assigned To should remain as the tester username. d. If the tester does not agree Enter additional information in the comments to help the developer with the issue. Update the Status to Reopen and update Assigned To back to the jrward. 6. A Development Lead will assign the work to available developers by updating the Assigned To field to the developer username. 7. The developer will update the Status to Open once they start working on it. 8. Developer finishes the development work. Development tool updates Status to Fixed and Assigned To updated to jrward (or PFW SIM Lead for Testing Group). 9. Once the initial testing is completed by MMS Test Eng, the Assigned To field is set to the OSS Lead. The OSS Lead and Tester will verify the issue. 10. OSS Lead/SIM Tester verifies the issue has been resolved. a. If issue has been resolved Tester enters comment with information and updates Status to Closed. This is sometimes completed by MMS Test Eng. b. If issue has NOT been resolved Tester enters comment with information on why it does not fix the issue, updates the Status to Reopen, and updates the Assigned To back to the OSS Lead username.

Filtering Defects
To Look Up a Specific Defect Number
Within the Defect grid, click the drop down arrow next to the Filter/Sort button. Select to Clear Filter/Sort. This will clear any current filters you have selected. It will prompt you before actually clearing the filter. In the Defect ID field (above the records), enter the Defect ID you are looking for and hit Enter. This will display only the Defect you are looking for.

To Create a Filter
Click the Filter/Sort button. The following screen will appear.

25

Within this screen you can set a filter condition based on the fields of your choice. For each field you can manually type your condition in the screen or click the ellipsis on the right side when your cursor is in the field. For fields with drop down values, the Filter Condition screen will look like the following screen.

You can use conditions with And, Or, etc to help filter your records. From the Filter screen you can also change the sort orders and groupings. Example of a query for all issues found during our testing in the May sprint: 1. Filter defects for System Testing and Regression Testing for the May Sprint. 2. Click on the Ellipsis for the Phase of project. 3. In the Select Filter Condition screen select System Testing from the list. 4. Select Or from the list on the right hand side 5. Select Regression Testing from the list. 6. Click OK. 7. Back on the Filter screen click the Ellipsis on the right side of the Quarter field. 8. Select May 2009 for the May sprint. 9. Click OK.

26

You can also create filters by using the spaces at the top of each column. An ellipsis will appear when clicking on any the white space of the column headings. Clicking on the ellipsis will bring up the Filter Condition screen as shown previously. You can also type your value right in the whitespace of that field.

Saving Your Filter as Public or Private

You can save your filters for future use. If this is a filter that you will only use, you may save it as a private filter. If this is a filter that will be used by many people (ex: filters for sim events) you can save it as a public filter. Go to Favorites menu and select Add to Favorites.

The following screen appears.

From this screen enter a name for your filter. Select if the filter should be a Private or Public filter. Click OK.

27

To pull up a private or public filter, from the Favorite field on the toolbar select the filter of your choice from the list. It will display all private and public filters.

28

General Information for Q.C.

Attachment Functionality

The above icons are used throughout Quality Center. These are the buttons used to attach documents, clients, report writers, and screen shots to your scripts or issues. - Attach File (CTRL+F) will bring up a browse window. You can attach many different file types with this method. - Attach URL (CTRL+W). The window that appears allows you to enter a URL as an attachment. - Snapshot tool. This tool allows you to take a screen shot and attach it. You do so by dragging the camera from the following window and dropping it on the window you would like a print screen of.

The screen you captured with this tool will appear in this window. Click Attach to save the screen shot. - This icon will gather the current state of your PC and attach it as shown in the screen below.

29

- If you have something copied into your clipboard by using CTRL+C or Copy function from the application you were using, you may attach that information with this button. This will create a file with the content and attach it.

Switching Between Projects without Logging Out of QC

In the Tools Menu, you are able to switch between projects without logging off and logging into a different project. This would be used to report issues to the Quality Center administrators or if you are assigned to more than one project (like MMS and Core Advanced).

In the Tools menu in the top right corner, select Change Project. From the options that display choose the project you would like to switch to. This will only display the projects that you have permissions to view.

Quality Center Help

We can use the Help on this page, Documentation Library, and Whats New? from the Help drop down button in the top right of the screen.

30

Some of the other options are specifically for the group that maintains Quality Center. They have a specific Customer ID that is required to get support or use the Knowledge Base.

How to Report Issues for Quality Center

Issues could be new users to the team, additional values or removing values from picklists, or actual issues with the system.

1. At the login screen for quality center, enter your password and uncheck the
Automatically log in to my last domain field (only if it was previously checked). 2. Click Authenticate or hit Enter on the keyboard. 3. In the Domain field, change from PAYX to CONFIGURATION_MANAGEMENT. 4. It should then default the Project to Tools_Administration. 5. Click Login.

31

6. Submit a New Defect for the issue or change.

7. Fill out all required fields. 8. Once selecting Quality Center for the Project field, some additional fields will appear. 9. Choose MMS_Projects from the Quality Center Project field. 10. Be sure to include all of the information in the Description field. 11. Do not alter the Assigned To field. This should remain as the default based on the Project. 12. Click OK when complete.

Current Issues Logged For Quality Center

Issue 1: When copy a step or series of steps that contain an attachment(s), the content of the attachment does not carry over. It looks as though it copied, but the file is 0 bytes. As a workaround please use the following steps: 1. In the Original Test Plan open the attachment view. 2. Use Save As to place the attachment in a local folder on your pc. 3. Copy the Design Step as normal. 4. Paste the Design Step into the new script you are creating. 5. In newly pasted step, delete the 0 byte attachment. 6. Using the Attach tool, attach the version you saved to your PC. Issue 2:

32

If Quality Center remains open with no activity and you have information entered on the details tab and a saved blank step, you will lose the information on the details tab when Quality Center automatically logs you out. Current work around is to log out of Quality Center before you are timed out or enter into another test plan, this will automatically save what has been written.

33

Additional Resources
How to search prior CRs
H:\Support\MMS\MMS_Implementation\Procedures\Testing_Scripting\Searching for prior CRs.doc

Testing Guidelines
H:\Support\MMS\MMS_Implementation\Procedures\Testing_Scripting\Guidelines for Scripts in Quality Center.doc

Testing Definitions
H:\Support\MMS\MMS_Implementation\Procedures\Testing_Scripting\TestDefinitions.doc

Developments Turnover Utility

Install location: \\corpnt07\mms_sh\Software\Utilities\TurnoverUtil\setup.exe

Refer to Help menu within the Turnover Utility for more information.

34