ALM User Guide Version 1.1

Views:
 
Category: Entertainment
     
 

Presentation Description

No description available.

Comments

By: bhavin76 (87 month(s) ago)

Michael can you please forward this ppt to me - bhavin76 ' a t ' gmail.com

Presentation Transcript

Application Lifecycle Management (ALM) TrainingNovember 2010 : 

Application Lifecycle Management (ALM) TrainingNovember 2010

Objectives : 

Objectives 1 I. Access ALM Login Navigation Toolbars II. Test Script Set-up Load/Create in Test Plan, and then Move to Test Lab Create a Test Set in the Test Lab Add Test Scripts to a Test Set III. Execution Run a Test Script IV. Log a Defect Add a new Defect Take a Screen Shot Defects Tab V. Defect Management Defect Status Role Definitions Defect Severity Defect Priority VI. Questions

Access ALM Login : 

Access ALM Login URL = http://144.36.42.112/qcbin Domain = Default Project = Symphony User ID = user name that was previously determined – Note: If your User ID is not pre- populated in the dropdown menu, you must enter it manually. (user ID for ALM sent by michael.l.harmon) Password = your password that was previously sent Refer to Section 8: Editing User Information in the Defect Job Aid for further instructions for setting UserID and Password Note: You will need to VPN into Ascension Health network if offsite before you will be able to get to ALM 2

Access ALM Navigation : 

Access ALM Navigation 3 Note: The side bar contains all functional areas of ALM Sidebar

Access ALM Navigation : 

Access ALM Navigation 4 Note: The side bar contains all functional areas of ALM Sidebar

Access ALM Toolbars : 

Access ALM Toolbars The common ALM toolbar is accessible from all functional areas of ALM located on the sidebar: 5 Project Name User Name

Test Case Set-upLoad/Create in Test Plan, Move to Test Lab : 

Test Case Set-upLoad/Create in Test Plan, Move to Test Lab 6 Test Plan Test Lab Test scripts will be created or loaded into the Test Plan (see Exporting to ALM Job Aid for instructions) Test scripts will be maintained and organized in the Test Plan. In order to execute test scripts created in the Test Plan, they must be moved to the Test Lab”

Test Script Set-up Create a Test Set in the Test Lab : 

Test Script Set-up Create a Test Set in the Test Lab 7 Click the New Folder button or choose Test Sets > New Folder. The New Folder dialog box opens Type the Folder Name and click OK. Note that a folder name cannot include the following special characters: /\?”%’<>* The new folder appears under Root in the test sets tree In the test sets tree, choose a folder and click the New Test Set button or choose Test Sets > New Test Set. The new Test Set dialog box opens In the Name box, type a name for the test set. Note that a test set name cannot include the following special characters: /\?”%’<>* Note: A description is not necessary for every Test Set

Test Script Set-up Add Test Scripts to a Test Set : 

Test Script Set-up Add Test Scripts to a Test Set Once you have created a folder and named your test sets, you must select scripts to be added to each test set. To do this, first make sure you have selected the test set to which you want to add scripts. Then, click the “Execution Grid” tab and select the “Select Tests” icon The Test Lab will display the Test Plan Tree. Select scripts to be added to the Test Set by dragging them into the middle section of the screen. Note: You may drag entire folders, or individual tests. If you drag an entire folder, a message will display confirming your desire to move the folder. Simply click OK to add the folder to the Test Set. 8 To customize the Test Lab View, click the icon from the Toolbar menu. The Select Columns window is displayed, where you can select which columns to display. Arrange the column order by using the Up and Down arrows on the right side.

Execution Run a Test Script : 

Execution Run a Test Script From the Test Lab tab, select the test script you want to run within your Test Set. Click the “Run” button on the toolbar: The Manual Runner dialog box opens (see below) Click the “Begin Run” button to start the test run. 9 5. The Step Details box opens 6. The script is populated in the Description and Expected boxes. Note: See Defect Job Aid for tips for viewing the Step Details Box

Execution Run a Test Script (cont.) : 

Execution Run a Test Script (cont.) 10 With the application open, perform the step indicated in the Description box. Determine if the expected result in the Expected box occurs. If expected result occurs, the step has passed. Click the “Pass Selected” icon on the Details Box If Expected result does NOT occur, populate the Actual text box, describing what did happen. This step has failed. Click the “Fail Selected” icon on the Details Box. If you have detected a new defect, select the “new defect” icon to begin logging a defect.

Log a Defect Add a New Defect : 

Log a Defect Add a New Defect 11 Upon clicking the “New Defect” icon from a script, or the “New Defect” button from the Defect grid, the following “New Defect” Dialog box appears. Complete all required (red with an asterisk) fields For Title: Short Defect Description Description: reference test data used, Script name, steps performed, description of defect Attach a screen shot (see defect job aid for instructions) Reference Defect Job Aid for Defect Field and value definitions When defect is complete, click the Submit button. Note: After adding, a blank dialog box will remain open - you will have to close the New Defect Dialog box to return to the Test Lab.

Log a Defect Take a Screen Shot : 

Log a Defect Take a Screen Shot 12 From the Add a Defect Dialog Box, click the camera icon The snapshot window opens. Directions state, “Drag and drop the camera icon to one of the windows on your desktop to capture it” Click the camera and drag it to the appropriate page to capture a screen shot of the defect you are logging After taking the picture, click the Attach button to attach the screenshot to the defect OR click Cancel to close the Snapshot window without saving screenshot The screen shot will appear attached to the defect. Right click the screen shot file and rename using the following convention: Functional Area_Name of Page_Area of Defect

Log a Defect The Defects Tab : 

Log a Defect The Defects Tab The Defect Page displays all defects logged to date, including defects with “Closed”, “Reject” or “Duplicate” status A user may filter defects on the Defects Page using the column headers. To do this, click the column header you want to sort by then click dropdown. 13 Helpful Hints On a daily basis, access the Defects Tab and filter by your user ID to determine which defects are assigned to you, or those that require clarification Filter by NOT Closed Or NOT Duplicate Or NOT Rejected to see defects that are still New, In Progress, or Open Select Filter Condition will appear. Select which values you wish to filter, and click OK. The Defect Grid will refresh to display your results.

Slide 15: 

14 A defect begins once it is logged, and will always start with a status of “New”. It then goes through a series of checkpoints to ensure it is properly captured, assigned, and resolved. The below diagram discusses the various ‘statuses’ of a defect: Defect Management Defect Status

Defect Management Role Definitions : 

Defect Management Role Definitions The following table defines the different roles in the Defect Process: 15

Defect Management Role Definitions : 

Defect Management Role Definitions The following table defines the different roles in the Defect Process: 16

Slide 18: 

17 Defect Management Defect Severity The below table display the severity categories that have been approved by the Symphony team. Each tester will assign an appropriate severity to each defect, which will then be reviewed by the Functional Team Lead.

Slide 19: 

18 Defect Management Defect Severity The below table display the severity categories that have been approved by the Symphony team. Each tester will assign an appropriate severity to each defect, which will then be reviewed by the Functional Team Lead.

Slide 20: 

19 Defect Management Defect Severity The below table display the severity categories that have been approved by the Symphony team. Each tester will assign an appropriate severity to each defect, which will then be reviewed by the Functional Team Lead.

Slide 21: 

20 Also defined and approved by the Symphony Team, each defect will be assigned a Defect Priority by the tester and then reviewed by the Functional Team Lead. The priority for a defect may change during its lifecycle depending on other critical path defects defined by the business stakeholders. Defect Management Defect Priority

Slide 22: 

21 Defect Management Defect Priority The below Service Level Agreements for each defect Priority have been defined by the overall System Integration Test Lead:

Questions : 

Questions 22

authorStream Live Help