pot.rational.09.2.066.01 workbook

8/4/2019 PoT.rational.09.2.066.01 Workbook

1/176

IBM Software Group

An IBM Proof of Technology

Collaborative Application LifecycleManagement Solutions from IBM Rational

Lab Exercises

2010 IBM Corporation


2/176

PoT.Rational.09.2.066.01

Copyright International Business Machines Corporation, 2009, 2010. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


3/176

IBM Software

Contents

LAB 1 UPDATE THE PRODUCT BACKLOG................................................................................................31.1 CREATE NEW REQUIREMENT AND ELABORATION ARTIFACTS.......................................................5 1.2 REVIEW THE REQUIREMENTS FOR THE SPRINT .........................................................................13 1.3 UPDATE THE PRODUCT BACKLOG ............................................................................................17

LAB 2 PLAN THE SPRINT...........................................................................................................................242.1 DESCRIBE HIGHEST PRIORITY FEATURES.................................................................................26 2.2 DEFINE SPRINT GOAL..............................................................................................................36 2.3 AGREE TO ITEMS FOR THE BACKLOG........................................................................................40 2.4 ADD DEVELOPMENT TASKS......................................................................................................46

LAB 3 MANAGE THE SPRINT.....................................................................................................................553.1 CREATE A COLLECTION OF REQUIREMENT ARTIFACTS FOR THE SPRINT .....................................56 3.2 ALIGN TEST SPRINT PLAN .......................................................................................................64 3.3 CHECK TEAM ALIGNMENT ........................................................................................................85

LAB 4 IMPLEMENT THE SPRINT PLAN ....................................................................................................894.1 CREATE TEST SCRIPTS AND TEST EXECUTION RECORDS ..........................................................89 4.2 DEVELOP SURFER SQUAWKER.................................................................................................97 4.3 MONITOR INTEGRATION BUILD ...............................................................................................112 4.4 MONITOR BUILD STATUS .......................................................................................................116

LAB 5 RESPOND TO A TEST FAILURE...................................................................................................1205.1 EXECUTE TEST AND SUBMIT DEFECT .....................................................................................121 5.2 TRIAGE DEFECTS ..................................................................................................................140 5.3 FIX DEFECT AND DELIVER CHANGE........................................................................................144 5.4 CONFIRM DEFECT IS FIXED....................................................................................................160

APPENDIX A. NOTICES.........................................................................................................................................167APPENDIX B. TRADEMARKS AND COPYRIGHTS..............................................................................................169

Contents Page 1


4/176

THIS PAGE INTENTIONALLY LEFT BLANK


5/176

IBM Software

Lab 1 Update the Product Backlog

Big plans, little plans, shifting plans, stagnant plans they all have the potential for becoming creativeexercises rather than reflections of reality. Many Agile teams have learned to execute against realisticplans by working with public task boards and moving a story requirement and its related tasks through

their phases to completion.

If you are part of a geographically dispersed team, or even a co-located team coordinating with other co-located teams in the context of a larger project, traditional approaches are inadequate. Planning in suchcircumstances tends towards an exercise in creative writing. In addition teams have multiple sources ofinformation to work with defects in one tool, requirements in another, resource information in another making it challenging to coordinate a plan.

Through the use of in-context collaboration for linking artifacts across disciplines and the use of dynamicplans where the data is coming directly from the work-items owned by the team members, youll see howthe plan can be a reflection reality.

In this lab you will create a new requirement and ensure the product backlog is ready for team review.

In Scrum, a product backlog is used to capture the work items for the project (this is similar to a releaseplan). The product backlog is owned by a product owner who works with the development and test teamsto determine which items can be moved into a sprint plan. The product owner's role is to represent thestakeholders by updating and prioritizing the product backlog.

In this scenario, Bob is the product owner. He needs: To review current product requirements and the ability to quickly create new requirements in context

Access & visibility into the development team plans

The ability to query the backlog as it relates to his requirements

The ability to prioritize the Backlog using the Web user interface (UI)

Check that all the key requirements are linked to work items in the product backlog and if notmake the appropriate updates.

Lab 1 Update the Product Backlog Page 3


6/176

IBM Software

Some Scrum Terms Defined

Product Backlog

The Product Backlog is the master list of all functionality desired in the product.

When a project is initiated there is no comprehensive, time-consuming effort towrite down all foreseeable tasks or requirements. Typically, a project team writesdown everything obvious, which is almost always more than enough for a firstsprint. The Product Backlog is then allowed to grow and change as more is learnedabout the product and its customers.

Sprint

An iteration of work during which an increment of product functionality isimplemented. A typical sprint lasts 2 weeks, although lengths of 1 week to 1 monthare not unusual. The content of a sprint is selected from the product backlog.

Story

Or, user story is a brief description of a user need. The product backlog ispopulated with stories. Each story has a relative priority and complexity. Stories aresized in relative units of effort called story points. For example, if one story is 1point and another is 2 points, the team is stating that they believe the second storywill take twice the effort of the first. Story points are intended to create groups ofstories that differ in effort by an order of magnitude. They are not meant to beprecise. Over time a team learns the number of story points it is typically able tocomplete in one sprint. This is the teams velocity.

Epic

A grouping of related stories. Typically used when a story is determined to be toobig to fit into one sprint. The story is decomposed into multiple stories and an epic

is created as the parent of the stories to preserve the overall goal.

Scrum

A short daily meeting where each team member shares what they accomplishedyesterday, what they will work on today and what, if anything, is blocking theirprogress. The scrum master takes ownership of all issues blocking progress.

Page 4 Collaborative Application Lifecycle Management Solutions from IBM Rational


7/176

IBM Software

1.1 Create New Requirement and Elaboration Artifacts

Lab Scenario

Bob just returned from an important stakeholder review with a

new idea for the project. First he needs to review the existingproduct requirements, and then he will document a newrequirement to understand its context in the application.

Team Role

You are performing the role of Bob, the product owner. In thissection, you will use IBM Rational Requirements Composerto create a new requirement and a corresponding work item forthe development team.

__1. Log into Rational Requirements Composer as Bob.

__a. Open IBM Rational Requirements Composer via the Tools menu in the lower right-handcorner of the desktop.

__i. Click Tools and select RRC IBM Rational Requirements Composer 2.0

__b. Click the Open button in the editor toolbar.



8/176

IBM Software

__c. ClickBobs Dashboard. It will display a dashboard with recent artifacts and comments,similar to the dashboard shown below.

Personal dashboards

Users have personal dashboards in Rational RequirementsComposer. This allows you to see activity across all theprojects you may be involved in.

__2. Open the Squawk project dashboard by clicking theOpen button in the editor toolbarand click the Squawk project. This displays only the Squawk project information.



9/176

IBM Software

Project Dashboards

Projects have dashboards in Rational RequirementsComposer. This provides project team members with aconsistent view of project information.

__3. As time allows, review current Squawk requirement artifacts. In theProject Explorer you willfind storyboards, user interface sketches, documents, and existing requirements.

For example you can follow steps a through e:

__a. Click on Glossary, double click Squawker

__b. Click on Stakeholder Needs, double click Squawk Inc Business Goals and Objectives

__c. Click onStakeholder Needs, double click Stakeholder and Responsibilities

__d. Expand User Story Elaborations, click on Roles and Personas, double clickonCertified Teacher Persona

__e. Expand User Story Elaborations, click on Storyboard, double clickon View a Surfersquawker

__f. Close any opened artifacts by clicking thex on the artifact tab.

Collapsing ViewsYou may need to collapse the Information view on the rightand make the project explorer on the left smaller to easilyview and browse artifacts.

__4. Create the new Surfer Squawker requirement.

__a. Return to the Squawk project dashboard by clicking the Squawk tab , if notalready selected. Make sure you have selected the Artifact tab within the Squawk Project.



10/176

IBM Software

__b. Click theCreate Artifact button and select the Requirementartifact type.

__c. Create the Surfer Squawker requirement with the following information:

__i. TypeSurfer Squawker in the Name field.

__ii. Ensure the Squawk project is selected in theProject field.

__iii. SelectRequirements in the Folder field.

__iv. Selectsprint 3 in the Tags field.

Tags are used here to specify the candidate sprints Bobwould like to see the requirement implemented. He will usethis to get organized when describing his priorities to theScrum team.

__v. Click theNext button and select the Story Requirement Types checkbox. Clickthe Finish button.



11/176

IBM Software

__vi. TypeA surfer squawks Calabunga, Dude! in the rich text field.

You may see a different requirement number next to theSurfer Squawker requirement. This is not a problem.

__vii. Select the following values in theAttribute Groups section of the Informationsidebar on the right-hand side of the workspace:

(1) Set Origin to Customer.

__viii. PressCtrl-Sto save the requirement



12/176

IBM Software

__5. Create a story work item for the Surfer Squawker requirement. This work item will be used bythe development team to track implementation of the new requirement.

__a. Expand theLinks section of the right-hand Information sidebar.

__b. Select theCreate Link button and select Implemented By

__i. Log into Rational Team Concert. EnterBob for both the User ID and Password

and then click Log In. If prompted regarding an invalid security certificate, clickYes.



13/176

IBM Software

Important!

The User ID and Password are case sensitive.

__ii. If you get an error message asking if you want to proceed, click Yes.

__c. EnsureSquawk is selected in the Project Areas field, and select the Create New radiobutton.

__d. Enter the following for the new Plan Item:

__i. TypeSurfer Squawker in the Summary field.

__ii. SelectBacklog in the Filed Against field.

__iii. SelectHigh in the Priority field.

__iv. SelectRelease 1.0 in the Planned For field.

__v. TypeImplement the Squawk requirement in the Description field.

__e. Click theOK button.

__f. Verify the new plan item by hovering over the Surfer Squawker item in the ImplementedBy field.



14/176

IBM Software

You may need to log in to Rational Team Concert again.

EnterBob for both the User ID and Password,

Tip: Use Rational Requirements Composer to create a broader context fordefining requirements

You can link Rational Requirements Composer requirements to any other RationalRequirements Composer artifacts that help describe the requirement artifacts like UIstoryboards, Use Cases, etc.

__g. Select the Create Link button and select Create a New Link for the Artifact.



15/176

IBM Software

__h. SelectChoose Existing Artifact, and expand the Squawk project to find the followingartifacts:

__i. User Story Elaborations Storyboard View a Surfer squawker. Linking arequirement to an artifact provides consumers of the artifact an easy way to seerelated artifacts that supplement the requirement definition.

__ii. ClickOK

__i. Repeat steps g - h and select another artifact.

__i. Stakeholder Needs Squawk Inc Business Goals and Objectives.doc __6. PressCtrl-S to save the requirement when you are done.

1.2 Review the Requirements for the Sprint__1. Review the requirements for the project and confirm that the key requirements are linked to work

items in the Product Backlog.



16/176

IBM Software

__a. SelectSquawk Project tab then the Requirements tab to view all the requirements for theproject

__b. Select thesprint 3 tag to view the requirements for Sprint 3 on the project.



17/176

IBM Software

__c. TheSurfer squawker requirement is included for Sprint 3. Bob needs to check that thisrequirement is associated with an appropriate work item so that it can be included in therelease backlog for Sprint 3. The current display does not show this. Select the

Configure column properties button in the top right hand corner of the window.

__d. Select theImplemented By checkbox and click OK. This will include the associatedRational Team Concert work items in the Requirements window.



18/176

IBM Software

__e. Note the same effect can be achieved by right-clicking the column heading bar andselecting the columns you want to display.

__f. Bob confirms that there is a work item associated with each requirement he would like

implemented in Sprint 3.

__2. Close or minimize Rational Requirements Composer.



19/176

IBM Software

1.3 Update the Product Backlog

Lab Scenario

Bob now needs to review the product backlog and prioritize thenew story requirement with regard to the other items. The team

is about to begin the next sprint, so this is his opportunity toprioritize the backlog and make sure his most important storiesare addressed by the team.

Team Role

You are still performing the role of Bob, the product owner. Inthis section, you will use the Rational Team Concert SquawkDev Web UI to review and prioritize the backlog for thedevelopment team.

__1. Log into the Rational Team Concert Squawk Dev Web UI as Bob.

__a. Start the Firefox Web browser via the icon in the Windows taskbar.

__b. SelectDashboards Squawk Dev from the browser bookmarks toolbar bar.



20/176

IBM Software

__c. EnterBob for both the User ID and Password, and then click Log In.

Important!

The User ID and Password are case sensitive.



21/176

IBM Software

__2. In the Squawk project area dashboard, look at theCurrent Squawk Plans viewlet and notice thecurrent sprint is Sprint 3. The Sprint 3 planning meeting is later today, and you have time to addthe new story to the Product Backlog before the meeting.

__3. Navigate to the product backlog

__a. Click theProduct Backlog link in the Current Squawk Plans viewlet.



22/176

IBM Software

__b. Click thePlanned Items link. This page provides several views of the items in the projectsplan. You will use a couple of them in this exercise. In any of the views, you see thecollection of Epic and Story work items planned for this release. Note the SurferSquawker story created from Rational Requirements Composer, and the blue circle nextto it. More on the blue circle in a bit. You will now use the Work Breakdown view toindicate the new work item is a child of an existing Epic. Choose the view from the View

As dropdown.



23/176

IBM Software

__4. Move theSurfer squawker story underAdd a wide variety of squawkers to the system epicusing drag and drop.

__a. ClickSurfer Squawker, hold the left mouse button, drag the plan item on top ofAdd awide variety of squawkers to the system.

__5. Bob knows that the surfer squawker is the highest priority item now, so check the priority in thebacklog and make adjustments so that the new Story is at the top of the list.

__a. SelectBacklog from the View As dropdown and note that the Surfer squawker story hasnot yet been ranked relative to the other stories. Note the blue informational icon (mayneed to refresh the plan to see it). Hovering over the icon will let you see the informationalmessage. This information will be available until you rank the Surfer squawker.



24/176

IBM Software

__b. Drag and drop the Surfer squawker to the top of the list above both epics. This ranks thestory ahead of all the other work in the backlog.

__c. If you wish, you may experiment with how the product backlog is fully ordered even amongitems of the same priority.

__i. For example, if you drag and drop the Surfer squawker down between two Lowpriority stories, the Surfer squawkers priority will change to match and it will beranked between them.

__ii. If you then, drag and drop it back up to the top, its priority will change back and itwill be ranked at the top again.

__iii. The rank is another piece of data on the work item in addition to the priority that ismanipulated via your drag and drop operations.

__d. Close Rational Team Concert

__6. Bob has confirmed that all the requirements identified for Sprint 3 are correctly associated towork items. Note that the work item has not been assigned to a plan. In the next lab RationalTeam Concert will be used to create an iteration plan for the work items for Sprint 3.



25/176

IBM Software


The backlog includes the work items that Bob identified ascandidates for Sprint 3. At this stage the Sprint Planning meetinghas not occurred and the iteration plan for Sprint 3 has not beencreated so changes might need to be made in order to balancethe overall work load for Sprint 3. The Rational Requirements

Composer and Rational Team Concert integration makes it easyto navigate between requirements and the work items toaccurately assess the workload and make the necessarychanges.

In the next lab you will create the iteration plan for Sprint 3 andassign work items to this sprint.

Conclusion

This concludes Lab 1. The product backlog now reflects theteams true requirements priorities. In the next lab, you willuse this backlog to plan the upcoming sprint.


26/176

IBM Software

Lab 2 Plan the Sprint

Agile teams drive their workload from the product backlog which needs to accurately reflect therequirements of the project. In many cases the project requirements can be effectively described in theepics and stories of the product backlog. However, sometimes it is beneficial to provide more detailed

definition to the entries in the product backlog. These more detailed requirements need to be kept in syncwith the product backlog and the sprint backlog in which they are being implemented.

IBM Rational Team Concert enables agile teams to manage their Iteration (or Sprint) plans using abacklog of prioritized work items. In Rational Team Concert 2.0, the Scrum process (among others) issupported enabling scrum teams to manage work using work item types, Sprint backlogs and processesspecific to scrum.

IBM Rational Requirements Composer provides a collaborative environment to capture, define, analyzeand refine the project requirements. Seamless integration of requirements with work items ensures theright requirements are included in each Sprint of the project.

In the 2.0 versions of Rational Team Concert and Rational Requirements Composer, requirements canbe linked to development work items. Whats particularly interesting in this integration is that analysts cancreate these links with little knowledge of Rational Team Concert and more importantly, without leavingthe Rational Requirements Composer client. Developers interacting with the work item in Rational TeamConcert can see the links to the requirements and can run queries to find all plan items that do not haverequirement links.

In this lab you will plan the next sprint.

At the start of each sprint, a sprint planning meeting is held. Sprint planning is typically divided into twoparts. During the first part, the product owner explains the prioritized product backlog and the full teamagrees on a sprint goal (a short description of what will be achieved). This part of the meeting is typicallyattended by the Product Owner, Scrum Master, the entire Scrum Team, and any interested and

appropriate management or customer representatives. In the second part of the meeting the scrum team,(made up of the development, analyst and test teams) meets on their own to select the stories they cancomplete during the upcoming sprint. Those selected stories are then moved from the product backlog tothe sprint backlog. When performing concurrent testing, testers align their test effort with the work itemsin the development sprint backlog.



27/176


28/176

IBM Software

2.1 Describe Highest Priority Features

Bob leads the discussion of the top priority features in theProduct Backlog. The scrum team will let him know when hehas clearly gone beyond the point in the list that can fit in the

sprint.

Team role

You are performing the role of Bob, the product owner. In thissection, you will use the Squawk Dev Web UI to describe thehighest priority features.

__1. Log into the Squawk Dev Web UI as Bob.

__a. Start the Firefox Web browser via the icon in the Windows taskbar.




29/176

IBM Software

__c. EnterBob for both the User ID and Password, and then click Log In.

Lab 2 Plan the Sprint Page 27


30/176

IBM Software

__2. Click theProduct Backlog link in the Current Squawk Plans viewlet on the right of the page.

__3. Click thePlanned Items link then, in the View As dropdown, select Backlog.



31/176

IBM Software

__4. The backlog shows the ordered set of epics and stories that have not yet been implemented.During the discussion the team needed to better understand the scope of the new SurferSquawker work item. This information is readily available through the integration betweenRational Team Concert and Rational Requirements Composer.

__a. Select theSurfer Squawker work item and the work item details are displayed.



32/176

IBM Software

__b. Bob can see that this work item implements one requirement. Click this link to view allthe links associated with the work item.



33/176

IBM Software

__c. The work Item links tab is displayed. Hover over theSurfer Squawker link and selectLog In to view more details of the requirement in Rational Requirements Composer.

__d. EnterBob for both the User ID and Password, and then click Log In.



34/176

IBM Software

__e. Now hovering over theSurfer Squawker link shows more information from RationalRequirements Composer. Select Surfer Squawker in the pop-up window to view thedetailed requirement information in Rational Requirements Composer.



35/176

IBM Software

__f. The requirement details are shown. Expand theLinks option in the bottom right handcorner to see other related requirements artifacts.

__g. TheSurfer Squawker requirement has a Squawk Inc. Business Goals document anda View a Surfer squawker story board associated with it.



36/176

IBM Software

__h. Using these links Bob and team are able to get a good understanding of the scope ofwork associated with this work item. Navigate back to the Rational Team Concertdashboard by selecting Dashboards Squawk Dev from the browser lower menu bar.

As described earlier, the backlog shows the ordered set of epicsand stories that have not yet been implemented. You areinterested in the highest priority stories that can fit in Sprint 3.Typically, several factors go into deciding what will go into asprint:

The discussion, led by the product owner Bob, aboutwhat the stories are, and why the ones at the top of thelist are the most important

How many story points the scrum team can be expectedto be able to implement in a sprint

And ultimately, the amount of work to which the team isready to commit

You will now see how these factors play out for Sprint 3 of thedevelopment of our simple application.



37/176


38/176

IBM Software

__b. Note theTeam Velocity viewlet in the middle column of the web page. This viewletshows the team completed 8 story points in Sprint 1, and 7 story points in Sprint 2. Theteam can use this history to understand roughly how much can fit in a sprint and controlhow far the team goes down the list during the discussion portion of the sprint planningmeeting.

Assume Bob has done a good job ordering the backlog and theteam understands and agrees with the ordering after thediscussion.

2.2 Define Sprint Goal

Team role

You will now switch to the role of Scott, the scrum master. In thissection, you will use the Squawk Dev Web UI to define the sprint goal.

The next thing to do in a sprint planning meeting is to define the sprint goal. When using Rational TeamConcert, the sprint goal is typically documented on the Overview page of the sprint plan. Scott, as thescrum master, typically creates and manages the sprint plan.



39/176

IBM Software


__1. Log out as Bob and then log in as Scott.

__a. ClickLog Out near the top right of the Web page.

__b. EnterScott for both the User ID and Password, and then click Log In.


40/176

IBM Software


__2. Create the Sprint 3 plan.

__a. SelectPlans near the top of the Web page.

__b. SelectCreate Plan on the left.


41/176

IBM Software


__c. In the entry field at the top of the plan, enterSprint 3 (1.0).

fo

Then, select the

llowing field values:

__i. Owner: Squawk Team - (Note, not Squawk but Squawk Team)

__ii. Iteration: Sprint 3 (1.0)- (should default to this value)

__d. In the upper right of the Web page, press Save.

__3. The plan is opened to thePlanned Items tab. Select the Overview tab to enter a sprint goal.

Teams may add other information about what they will be doing using the free text areaprovided.

__4. Enter our sprint goal now.

__a. At the upper right of theOverview tab, press the edit icon .

__b. Type in the following:The goal of sprint three is to implement theSurfer squawker and support the selection of multiple squawkers

in the GUI display.

__c. At the upper right of theOverview tab, press Save. You can also click the edit iconagain to close the edit widget and see your sprint goal on the Overview page.


42/176

IBM Software


In the second part of sprint planning, the scrum team continues the meeting to determine exactly wwill commit to implementing in Sprint

hichstories they 3.

2.3 Agree To Items for the Backlog

Team role

You are performing the role of Scott, the scrum master. In this section,you will use the Squawk Dev Web UI to agree to items assigned to theupcoming sprint,

they must include the new SurferSquawkerstory and the Enable showing multiple squawkers in the main windowstory. To easily

ver over the Related Plans link in the top right hand corner of the sprint plan to see allrelated plans.

__1. Given the goal of the sprint, the team quickly agrees that

switch between the product backlog and the sprint 3 plan as you plan:

__a. Ho

__b. Click theProduct Backlog in the hover window.

__c. Click thePlanned Items tab. If not already selected, select Iterations in the View Asdropdown.


43/176

IBM Software


__d. If the display shows a tree structure, change this by editing the view. The tree structureshows dependencies between work items and epics however, you need to be able to seethe rank order of work items to determine which work items should be included in sprint

ect the Edit View icon3. If a tree structure is displayed sel in the top right handbe Flat and Save

corner of the plan, select the Style to the changes.

__2. Move th ing multiple squawkers in the main window story into sprint 3.

__a. lick theEnable showing multiple squawkers in the main window story and an inplace editor for the story will be displayed. Set the fields of the story as follows:

e Enable show

C

__i. Filed Against: GUI

__ii. Owned by: Marco

__iii. Planned For: Sprint 3 (1.0)


44/176

IBM Software


__b. ClickSave and Close at the top right of the in place editor.

__c. The story you edited is now included in Sprint 3. Expand the Sprint 3 (1.0)view and you will see it there.


45/176

IBM Software


__3. Move the newSurfer squawker story into sprint 3.

__a. Still in theProduct Backlog, as before, click the Surfer Squawker story and an in placeeditor for the story will be displayed. Make these changes:

__i. Filed Against: Squawkers/People

__ii. Story Points: 1 pt

__iii. Owned by: Deb

__iv. Planned For: Sprint 3 (1.0)

Note based on an earlier sprint planning meeting the difficulty of this story wasagreed to be 1. Scott updates the story points to reflect this.



46/176

IBM Software


__4. Note that the team now has 6 story points committed for Sprint 3. Look at the progress indicatorin the shaded Sprint 3 (1.0) bar (see screen shot). As you saw in the Team Velocity viewlet, theteam can take on a little bit more work (1 or 2 more story points).

__a. You can see the next highest priority story is the Web UI story; however, it is estimated at5 story points and could not possibly fit in Sprint 3. The next highest priority story is theMark Twain squawker story. The team can commit to that. As before, click the MarkTwain squawker story and an in place editor for the story will be displayed. Make thesechanges:

__i. Filed Against: Squawkers/People

__ii. Owned by: Deb

__iii. Planned For: Sprint 3 (1.0)


47/176

IBM Software



__5. Note that Sprint 3 is planned with an appropriate number of committed stories based on theteams velocity.

Hover__6.

__7. tton at the top right of the plan editor to see all the updates that you already

over the Related Plans link in the top right hand corner of the sprint plan and select theSprint 3 (1.0) related plan.

Click the refresh bu

accomplished.


48/176

IBM Software


2.4 Development TasksAdd

Team role

You are performing the role of Scott, the scrum master. In this section,you and the team will use the Squawk Dev Web UI to add developmentimplementation tasks to the sprint plan.

__1. Typically at this point, the team would add child implementation tasks under each story and giveeach task a sizing in time (days and hours). In order to save time this has been partiallycompleted for you.

__2. You have a little work to do. Since the Surfer squawker was added during a previous lab, youwere not able to add child tasks to it for you before the workshop started. However, the tasks

have been completed ahead of time for you. You will only need to set up the parent/childrelationship.

e not done so already, underDeb, click the triangle icon__a. If you hav next to the Add awide variety of squawkers to the system epic in order to see the Surfer squawkerstory work item.

__b. Click the number to the very right of theSurfer squawker story to open the full editor forthe story.


49/176

IBM Software


__c. Click theLinks tab.

__3. In theLinks section, click the Add dropdown and select Children.


50/176

IBM Software


__a. In theAdd Link: ChildC

ren dialog, type surfer in the Use Work Item ID or Wordsontained in the Text entry field. Wait a moment and several work items will appear in

the list.


51/176

IBM Software


__b. Select theImplement Surfer squawker and its JUnit test case and Document Susquawker tasks.

rfer

__c. ClickOK in the dialog.

__d. ClickSave in the top right of the story editor.


52/176

IBM Software


__4. In order to help keep these and other predefined tasks hidden up to this point; the target sprinthad not previously been set. You will do that now.

__a. On the left underMy Queries, click the Sprint 3 pre-created tasks query.

__b. Click theEdit Multiple Work Items icon near the top right of the Web page

.


53/176

IBM Software


__c. Click the check box to the left of the result set headings row. This selects all the rows inthe result set.

__d. Click the green cross next to thePlanned For column heading.

__e. Within theEdit Multiple Work Items box, select Sprint 3 (1.0) in the Planned For box.

__f. To the right of theEdit Multiple Work Items title bar, click the Run.,. icon . If askedif you would like to modify work items, select OK. Please allow a few moments for thequery to run. If you see a message that starts with Operation Complete and asks aboutrefreshing the query, click OK.

__g. Close theEdit Multiple Work Items by clicking the X in the top right hand corner of thewindow.


54/176

IBM Software


__5. Select thePlans link in the bar near the top of the Web page to return to the Sprint 3 (1.0) plan.All the tasks are now part of the plan.

You may need to click the refresh icon to see them all.


55/176


56/176


57/176

IBM Software

Lab 3 Manage the Sprint

With the sprint planning meeting complete and the sprint backlog created, it is now time to ensure that allartifacts (requirements, development and testing) have traceable links to one another to effectivelymanage the sprint.

The previous lab highlighted the roles of Product Owner, Scrum Master and the Development Lead. It isnow time to focus on the role of the Test Lead to ensure that test plans are aligned with both the sprintdevelopment work items and the sprint backlog requirements.

So far youve utilized Rational Requirements Composer to assist in quickly identifying sprintrequirements and Rational Team Concert to define the sprint backlog of work items. To help with themanagement of quality artifacts, youll employ the use of Rational Quality Manager.

Rational Quality Manager provides a collaborative environment for test planning, construction, andexecution. Testers can create, manage and measure their effectiveness using Test Plans, Test Cases,Test Scripts, Execution Records and Results.

With the 2.0 versions of Rational Requirements Composer, Rational Team Concert and Rational QualityManager, a user can now seamlessly link test artifacts to development work items and requirements. Therobust integration of these products provides users with a powerful mechanism to communicate andcreate strong relationships across the requirement, development and quality disciplines of the softwaredevelopment lifecycle.

Lab 3 Manage the Sprint Page 55


58/176

IBM Software

In this scenario:

Bob starts by creating a collection of sprint 3 requirement artifacts. This collection isused to effectively manage not only the sprint 3 requirements, but also related elaborationassets, such as, storyboards or business process models.

Tanuj needs to align his test effort with the development sprint

Scott does a sanity check to see that test plans are in alignment with both sprint workitems and requirements

3.1 Create a Collection of Requirement Artifacts for the Sprint

In this activity, Bob, the Product Owner, will use Rational Requirements Composer to identify a collectionof requirement artifacts to be aligned with the sprint. One significant advantage of utilizing a collection ofrequirements artifacts is that it allows the stakeholder to see the requirements and all of their associatedelaboration artifacts (e.g., storyboards, use cases, business process models, etc.) in a single location.Ultimately this collection of requirement artifacts yields value to stakeholders across the developmentlifecycle as these collections are easily linked to/from related work items and/or test assets.



59/176

IBM Software

__1. Log into Rational Requirements Composer as Bob (if Rational Requirements Composer is notalready up and running)

__a. From the Windows taskbar, click Tools RRC IBM Rational Requirements Composer2.0

.

__2. Ensure that theSquawk project is open

__a. Click theOpen button and select the Squawk project from the pull-down menu



60/176

IBM Software

__b. This reveals the project dashboard view which looks something like below, depending onthe state that Rational Requirements Composer was last left in:



61/176

IBM Software

__3. Create a collection of requirement artifacts related to the sprint.

__a. Click theArtifacts tab. Choose the sprint 3 tag filter to quickly identify thoserequirements artifacts which are associated with (and previously tagged as candidatesfor) Sprint 3. Make sure that the Selected Filters pane on the left side of the interfacelooks like the following (i.e., the Tag: sprint 3 is the only filter selected):



62/176

IBM Software

__b. Click theView as list with details button labeled below to see more completeinformation about each of the artifacts. You should see five (5) different requirementartifacts with the sprint 3 filter applied from the Artifacts tab.



63/176

IBM Software

__c. Select the first artifact and then scroll down to the last artifact listed and perform a shift-click to select all artifacts tagged as sprint 3. With all artifacts selected, right-click andselect Add to New Collection to create a new collection of requirements artifacts.(Note: when selecting the requirements artifacts for inclusion in the collection, be sure toclick in the blank spaces where theres no active link text that may accidentally beselected)

With the details for each artifact displayed, you can see from the icons there are morethan standard requirements theres also a storyboard (named View a Surfersquawker).



64/176

IBM Software

__d. A dialog for the collection creation wizard pops up. Enter at least the following values:

__i. Name: sprint 3 collection

__ii. Project: rrc/Squawk (default)

__iii. Folder: Collections

__e. ClickFinish



65/176

IBM Software

__f. A new tab (calledsprint 3 collection) is created on the dashboard and it displays thenewly created collection artifacts along with the three buttons that allow the user tomanage the collection. Later in this lab, this requirement collection will be aligned withboth the sprint development plan and the accompanying test plan.

__g. Close Requirements Composer (File Exit from the pull-down menu)

In this activity youve demonstrated how to effectivelycreate a collection of related requirement assets to assist in

sprint planning. You will later see the robust toolintegrations to see how one can easily associate thiscollection of requirement assets with the sprints test plan.



66/176

IBM Software

3.2 Align Test Sprint Plan

In this section you will learn how to associate the sprint test plan with the collection of requirementsidentified for this sprint, while also aligning test cases with planning-level work items on the sprint

backlog.

By linking test cases to developer work items, testers gain transparency into the status of thedevelopment work and developers gain transparency into test coverage and test status for each workitem on the backlog. Similarly by linking test cases to requirements, analysts gain transparency into teststatus and coverage while testers gain access to supporting requirements information for their tests.Reporting on this linking provides invaluable information on the accuracy and completeness ofrequirements, work items and test cases. This enables the team to collaborate on the sprint plan withinsight to the effort of the whole team.

Since Tanuj has just participated in the sprint planning meeting, hes aware that there was a new entryadded to the sprint. He can also run a report to show this information. Given this, he knows that he haswork to do in creating and aligning the test plan with both the squawker requirements and the squawkerwork items of the sprint plan. Tanuj will start by logging into Rational Team Concert and running a test toconfirm his belief that there are gaps in the alignment of test cases to work items. He will develop testcases for the surfer squawker functionality and align them with both the development work items and therequirements.

The team will need new test cases for all the stories beingimplemented in sprint 3. For brevity, you will just create a testcase for the surfer squawker.

Team role

You are performing the role of Tanuj, the test lead. In thissection, you will use the SquawkQM Web UI from RationalQuality Manager to align the test sprint plan.



67/176

IBM Software

__1. Log in to Rational Team Concert as Tanuj

__a. Start the Firefox Web browser via the icon in the Windows taskbar


__c. EnterTanuj for both the User ID and Password, and then press Log In.



68/176

IBM Software

__d. Select theWork Items tab, then look under the Shared Queries pane on the left side ofthe interface. Open the C/ALM Traceability Queries and then click the Plan items withno test case (current iteration)

__e. The result should show a report similar to the following:

This tells Tanuj that there are at least a handful of work items which currently have notest cases associated with them. Tanuj will now leave Rational Team Concert and useRational Quality Manager in order to create a new test case. In the interest of time, youllsimply create a test case to align with the recently created Surfer Squawker work item.



69/176

IBM Software

__2. Tanuj will now log in to Rational Quality Manager to create the test case for the SurferSquawker work item

__a. In the Windows taskbar, click Tools RQM IBM Rational Quality Manager.

__b. EnterTanuj for both the User ID and Password, and then press Log In.



70/176

IBM Software

__3. Open the projects test plan

__a. Select theView Test Plans item from the Planning menu at the top of the web page.

__b. Click theSquawk 1.0 Test Plan in the display.



71/176

IBM Software

__c. The result should look like this where theres now aSquawk 1.0 Test Plan tab. Note theTable of Contents pane on the left which shows the various components of a test plan.

__4. Associate theSquawk 1.0 Test Plan with the sprint requirement collection that Bob has recentlycreated.

__a. From theSquawk 1.0 Test Plan, select the Requirement Collection Links text linkunder the Table of Contents pane. Once selected, you will see the following:



72/176

IBM Software

__b. From theRequirement Collection Links pane, you can add the sprint 3 requirementscollection that Bob created at the start of this lab. This is accomplished by clicking on the

in the Requirement Collection Links pane.

__c. The following dialog box appears asking Tanuj to login to Rational RequirementsComposer.



73/176

IBM Software

__d. A dialog appears with a list of all requirement collections found in the users projectspace. Presently, there is only one collection, so simply select the sprint 3 collectionentry and click OK.

__e. You are now returned to theRequirement Collection Links pane for the Squawk 1.0Test Plan in Rational Quality Manager. Notice that theres now a navigable link to thesprint 3 collection of requirements in Rational Requirements Composer.



74/176

IBM Software

__f. At this point its a good time to save the test plan by pressing one of the Save buttons onthe interface.

__g. Click on thesprint 3 collection link to see the collection of requirements in RationalRequirements Composer that are now associated with this test plan. The Web userinterface for Rational Requirements Composer is opened up in a new tab on the browser.Displayed on the dashboard are the requirements that you had previously committed to a

collection in the beginning of this lab.



75/176

IBM Software

__h. Return to theSquawk 1.0 Test Plan in Rational Quality Manager by selecting the TestPlan: Squawk 1.0 Test Plan tab on the browser.

You now have Squawk 1.0 Test Plan associated with the sprint 3 requirementscollection which will come in handy to ensure that youve sufficiently mapped all sprintrequirements to a test artifact. Furthermore, this provides Tanuj with easy access torelated requirements assets beyond just declarative statements (e.g., storyboards, usecases, or business process models) in order to get a comprehensive scope of the testcases required.

__5. With your collection of requirements aligned with the test plan, its now time for Tanuj to focus oncreating a new test case to validate the Surfer Squawker requirement.

__a. With theSprint 1.0 Test Plan tab still open, select the Test Cases section of the Tableof Contents



76/176

IBM Software

__b. ClickAdd New Test Case icon to create a new test case for the test plan.

__c. Complete theNew Test Case dialog with the following information:

Field Entry

GUI SurferName

Verify the Surfer squawker

in the GUI.Description

Squawk CALM Test Case

TemplateTemplate

100Weight

TanujOwner

Category GUI



77/176

IBM Software

__d. ClickOK on the New Test Case dialog

__e. ClickSave at the top right of the test plan to save the test plan changes made thus far.



78/176

IBM Software

__6. Associate new test case to the story it is validating

__a. Click theGUI Surfer link to open the new test case (in order to find the GUI Surfer testcase, you will need to click the Next link at the top or bottom of the list of test cases).

__b. TheGUI Surfer test case Summary is then displayed



79/176

IBM Software

__c. Select thePlan Items section from the Table of Contents on the left in order toassociate the new test case with a work item.

__d. Click theAdd plan items icon near the top right of the Plan Items pane.

__i. If prompted to log into Rational Team Concert, log in as Tanuj.



80/176

IBM Software

__e. The Rational Team ConcertPlan Item dialog is displayed and you may now search foran implementation plan item to align with this test case.

__i. Typesurfer into the Use Work Item ID or Words Contained in the Text field

and a search will automatically run.

__ii. Under theMatching Work Items text box, click the Surfer Squawker story andclick OK.

__f. Youll now notice a text link to theSurfer Squawker plan item showing that the GUISurfer test case is linked to the Surfer Squawker plan item. Click Save at the top right

of the test case to save the link.



81/176

IBM Software

__g. With the mouse, hover over theSurfer Squawker story link in the Plan Items list to seeinformation about the story.

__h. Click theSurfer Squawker link to follow it to the full work item interface in the RationalTeam Concert Web UI. Note that the story work item for the Surfer Squawker opens in anew tab on the browser. (Note: If prompted, log in as Tanuj)



82/176

IBM Software

A new tab opens up on the browser and the details of the Surfer Squawker work item aredisplayed

__i. With theSurfer Squawker story work item interface now open, click the Links tab.Notice the navigable links that the work item has with its supporting test case andrequirement.



83/176

IBM Software

This view of the Surfer Squawker work item reflects thestrength in the lifecycle solution by indicating the navigablelinks to both the test case which validates this story workitem as well as the requirement that it implements.

__7. Tanuj has one remaining task as part of align the test plan. He needs to associate the new testcase with the Surfer Squawker requirement.

__a. First, you can close out theSurfer Squawker work item tab, by clicking the on thetab.

__b. Now click back on theTest Case: GUI Surfer tab which will make Rational Quality

Manager available.

__c. Click theRequirement Links entry in the Table of Contents and the Requirement Linkspane will open



84/176

IBM Software

__d. Click theAdd new links icon on the right side of the Requirement Links pane

__i. The followingRequirement links dialog box is displayed, providing Tanuj theopportunity to search for and select requirements to associate with the GUISurfer test case.



85/176

IBM Software

__ii. First typeSurfer into the search box, Use Artifact Name or Words Containedin the Text:. Then click the Requirements folder and the Surfer Squawkerrequirement will be displayed in the Matching Artifacts pane.

Select SurferSquawker in the Matching Artifacts pane and then click OK tocomplete the association of this requirement with the GUI Surfer test case.

__e. TheSurfer Squawker requirement link is now displayed on the Requirement Linkspane for the GUI Surfer test case. Click the Save button to save this change to the testcase.

This Surfer Squawker link can now be used to navigate to the Rational RequirementsComposer Web interface to show the details of this requirement if you so desire. In theinterest of time, youll move along.



86/176

IBM Software

__8. Log out of all tool instances (Rational Requirements Composer, Rational Team Concert orRational Quality Manager) and close your browser. You will be switching back to the role ofScott, the scrum master, for the next section.

At this point, Tanuj has completed his part of the sprint

planning work. He has associated his Squawk 1.0 TestPlan (in Rational Quality Manager) with a collection ofrequirements (in Rational Requirements Composer). Hehas created a new test case for the test plan that alignswith a work item as part of the Sprint Plan (in RationalTeam Concert). Finally, he has tied this test case to arequirement, thus providing requirement-to-work item-to-test case lifecycle traceability.

As the sprint progresses, he will implement and run testscripts. You will see that in the next lab.



87/176


88/176

IBM Software

__c. EnterScott for both the User ID and Password, and then click Log In.



89/176

IBM Software

__2. Scott has already built a work item query that will produce the results hes looking for. At thispoint hes trying to ensure that all work items for this sprint have both requirements and testcases associated with them.

__a. Click theWork Items link at the top of the Web page.

__b. On the left pane, under My Queries, click the query called, Current sprint storiestraceability to requirements and test cases



90/176

IBM Software


__c. Upon executing the query, Scott takes note of the fact that story ids 14 (Mark TwainSquawker) and 22 (Enable showing multiple squawkers in the main window)currently have no test case associated with them. Hell want to ensure that theappropriate test cases are eventually identified to align with the work item (andrequirement). This query has done its job in identifying a gap in test case coverage. Thisseems like the type of report that would be placed on the projects dashboard.

__d. Log out and close your browser.

Conclusion

This concludes the Lab. The team now has a completesprint plan and is ready to get to work. You have seen howthe product backlog can be used to plan a sprint and howrequirements, test cases and stories can be linked acrossthe Rational Requirements Composer, Rational TeamConcert and Rational Query Manager repositories. In thefollowing labs, this link will help the team work moreefficiently and accurately.


91/176

IBM Software

Lab 4 Implement the Sprint Plan

The scrum team is ready to implement and test Sprint 3. In this lab you will explore how everyone canremain aware of each others progress, even across different tools.

In this scenario:

Tanuj creates test scripts and test execution records to be used for the current sprint.

Deb implements the new squawker code, as well as documentation and unit test cases. Indoing so, she refers back to the original requirement (maintained in Rational RequirementsComposer) from a link inside the Rational Team Concert story. She then initiates a buildagainst her new code.

Tanuj monitors the state of the build to understand when he can start with his testing efforts.

4.1 Create Test Scripts and Test Execution Records

Team role

You are performing the role of Tanuj, the test lead. In this section, youwill use the Rational Quality Manager tool to create test scripts and testexecution records.

This lab picks up where you left off at the end of the last lab. You have finished your planning work andare now ready to start your part of the sprint 3 implementation.

__1. Log in to Rational Quality Manager as Tanuj

__a. In the Windows taskbar, clickTools RQM IBM Rational Quality Manager.

Lab 4 Implement the Sprint Plan Page 89


92/176

IBM Software

__b. EnterTanuj for both the User ID and Password, and then press Log In.



93/176

IBM Software

__c. In theMy Tasks section of Tanujs Dashboard, select the GUI Surfer test case. You mayneed to scroll down through the list. Note that Tanuj could jump to the associated story(maintained in Rational Team Concert) and/or requirements (and their associatedartifacts maintained in Rational Requirements Composer) to get the info he needs tocreate the test case if he wanted to at this point.

__d. Select theTest Scripts section of the Table of Contents.

__2. Normally, you would create a new test script at this point. However, to save time, this step hasalready been completed for you.

__a. Click theAdd Existing Test Scripts icon.



94/176

IBM Software

__b. In theAdd Test Scripts dialog, place your mouse over the View Builder section at the top

of the dialog and the Expand icon will appear to the right. Click that icon to see thefields to change the filtering in the dialog.

__c. EnterSurfer in the Name field and then click Run in the View Builder area of the AddTest Scripts dialog.

__d. Check the box next to GUI Surfer.

__e. ClickOK to associate the test script to the test case.



95/176

IBM Software

__f. ClickSave at the top right to save the test case.

__g. Explore theGUI Surfer test script.

__i. Click theGUI Surfer test script in the Test Scripts list.

__ii. Review the steps for running the application, selecting the surfer, and verifyingthe graphic and text.



96/176

IBM Software

__iii. Close theGUI Surfer test script and return to the test case. (Hover over the GUISurfer Test Script tab to make the X icon appear)

__h. In theParent Test Plan(s) section of the GUI Surfer test case, select the Squawk 1.0Test Plan.



97/176

IBM Software

__3. Create test execution records for Sprint 3. Test execution records map the test environmentinformation to the test case, and are used to track progress on executing all the tests for Sprint 3.

__a. In the test plan, click theTest Cases section in the Table of Contents.

__b. Check the box to the left of the headings row of the list of test cases. This selects all thetest cases.

__c. Click theGenerate New Test Execution Records icon. This is how you specify that

you want to test the new functionality added to Sprint 3 (S3) in the Windows environment.If you also wanted to test the new code under, say, Linux you could do so bygenerating a similar set of test execution records. Executing this operation generatestest execution records for each test case that are used to track tests that are doneagainst the new S3 functionality.



98/176

IBM Software

__d. In theGenerate Test Execution Records dialog:

__i. SelectS3 for the Test Milestone in the Overview section on the left.

__ii. CheckWindows in the Reuse Existing Test Environments tab of theEnvironment area.

__iii. ClickNext > twice, then Finish. Save these changes by clicking the Savebutton.

__4. View the test execution records you just created. You will use a couple of them later.

__a. SelectView Test Execution Records from the Execution menu at the top of the Webpage.

__b. If prompted to log into Rational Team Concert, log in as Tanuj.



99/176

IBM Software

__c. Change theGroup By selection to Test Milestone. This will group the list intomilestones. Scroll down to the grouping of execution records for Sprint 3 to verify therecords you just created exist (you may have to scroll down several pages).

__d. Log out of Rational Quality Manager and close the browser window.

4.2 Develop Surfer Squawker

Deb is ready to begin working on her Sprint 3 work items. Shewill implement the Surfer squawker and its JUnit test case first.She will then run a personal build, and deliver her changes tothe stream so that others can use them.

Team role

You are performing the role of Deb, a Developer. In thissection, you will use the Rational Team Concert tool to developthe Surfer squawker.



100/176

IBM Software

__1. Open the Rational Team Concert client using Debs workspace.

__a. In the Windows taskbar, clickToolsRTCIBM Rational Team Concert.

__2. Deb plans her work and gets started.

__a. Click theMy Work tab in the upper left corner of the screen.



101/176

IBM Software

__b. Debs work from the Sprint planning meeting is in her Inbox in the My Work view. Clickthe accept all work link to accept the work from the Inbox.

__c. Deb knows Tanuj is anxious to test the high priority Surfer squawker, so she decides shewill work on that first. Drag and drop the Implement the Surfer squawker and its JUnittest case work item to the top of the list (right under Today). The rest of the team will beaware of her intended order of work via the Sprint 3 plan.

__d. She thinks she understands what she needs to implement and document based on theinformation in the Rational Team Concert work item, but just to make sure she decides togo back and reread the actual requirement.



102/176

IBM Software

__i. Double-click theSurfer squawker work item story to open it. One place to findthe story is within the My Work view. You could also navigate to the story viathe Links tab of the Implement the Surfer squawker and its JUnit test casework item. Note that stories (as opposed to other work item types such as tasks)

have an icon like this in the list:



103/176

IBM Software

__ii. From the work item, click theLinks tab.

__iii. From here, Deb can see a link to the requirement (Surfer Squawker) that thisstory implements. Double-click the Surfer Squawker link under ImplementsRequirement to open the actual requirement.

__iv. If prompted to log into Rational Requirements Composer, log in as Deb (selectYes if you receive a Security Alert).



104/176

IBM Software

__v. Look through the details of the requirement. Notice how it indicates in the Linkssection that this requirement is implemented by the Surfer squawker story. Debcould browse the associated elaboration artifacts of this requirement if desired.Close this tab when finished.

__vi. Close the Surfer Squawker story.



105/176

IBM Software

__e. Drag and drop theDocument the Surfer squawker work item to be right after theimplementation task you just planned. Notice how some other items move to tomorrowautomatically. This is due to the estimated size of the items you just planned for today.Note that the exact behavior of what moves to tomorrow (or even next week if today is aFriday) depends on what time of day it is when you perform this step. If it is late, even thedocumentation task you just dropped could move. (Note: If you prefer, you can right-click

the work item and select Move Up instead of Drag and drop.)

__f. Double-click theImplement the Surfer squawker and JUnit test case work item toopen it.

__3. Create the Surfer Squawker and its Test Case.

At this point, Deb would develop her Surfer squawker code and testcase, and update the squawkers JUnit test suite. In order to savetime, the code has been developed for you, and is available in achange set. You simply need to accept the changes.



106/176

IBM Software

__a. From the work item, click theLinks tab.



107/176

IBM Software

__b. In theLinks section, notice a change set associated with this particular work item isavailable. Right-click the change set, and click Accept in order to receive Debs code.These changes were performed ahead of time in another workspace as part of the labsetup. Accepting them into Debs current workspace updates her environment with thesechanges and simulates her development work for this lab. This also illustrates one waythat developers can share ad hoc changes with each other.

__4. Normally, Deb would run some tests and perhaps run a personal build to make sure her changesare all good. This code you accepted has already been tested, so you will take a chance byskipping this important step to save valuable workshop time.

A personal build does not impact the project build definition status,and runs on a repository workspace you specify. You run apersonal build of the latest project source code with the changes inyour own workspace. This allows you to test your changes beforedelivering them to the stream for others to use.



108/176

IBM Software

__5. Deliver squawker code to make it accessible to the rest of the team

__a. Check thePending Changes view in the lower section of the screen. The icon next tothe Core Component indicates that you have pending outgoing changes. Expand theOutgoing folder to view your changes.

__b. Right-clickCore and select Deliver to send your changes to the stream.



109/176

IBM Software

__6. Mark the task Complete.

__a. TheImplement the Surfer squawker and its JUnit test case work item is still open.Make sure youre on the Overview tab.

__b. From the status dropdown, selectComplete and then click Save. This marks this task as

Done.

__c. Close theImplement the Surfer squawker and its JUnit test case work item.



110/176

IBM Software

__7. Go back to theMy Work view and double-click the Document the Surfer squawker work itemto open it. Change its status from New to Start Working, then click Save.

__8. Create the Surfer Squawker documentation.

At this point, Deb would develop her Surfer documentation. In orderto save time, the documentation has been developed for you, and isavailable in a change set. You simply need to accept the changes.



111/176

IBM Software

__a. From the work item, click theLinks tab.



112/176

IBM Software

__b. In theLinks section, notice a change set associated with this particular work item isavailable. Right-click the change set, and click Accept in order to receive Debsdocumentation.



113/176

IBM Software

__9. Deliver the squawker documentation to make it accessible to the rest of the team.

__a. Check thePending Changes view in the lower section of the screen. The icon next tothe Core Component indicates that you have pending outgoing changes. Expand theOutgoing folder to view your changes.

__b. Right-clickDocumentation and select Deliver to send your changes to the stream.



114/176

IBM Software

__10. Mark the task Complete.

__a. TheDocument the Surfer squawker work item is still open. Make sure you are on theOverview tab.

__b. From the status dropdown, selectComplete and then click Save. This marks this task as

Done.

__11. From theLinks tab of the Document the Surfer squawker work item, double-click the link tothe Surfer squawker parent story. You will need this story after the build completes in the nextsection.

__12. Close theDocument the Surfer squawker work item.

4.3 Monitor Integration Build

Deb ensures that the continuous team build does not break as aresult of her changes. Builds can be scheduled to run on aspecific frequency of the teams choice; but, in this case, Deb

will manually request the build. Once she confirms the build issuccessful, she will tag it so that Tanuj knows the build is readyto test.

Team role

You are performing the role of Deb, a Developer. In thissection, you will use Rational Team Concert to monitor theintegration build.



115/176

IBM Software

__1. Request a build.

__a. Select theTeam Artifacts view on the left side of the Rational Team Concert window.

__b. ExpandSquawk Builds and right-click the workshop.squawk.build definition. Selectthe Request Build action.

__c. In theRequest Build dialog click Submit.



116/176

IBM Software

__d. TheBuilds view will open showing the new build. The build will finish in a minute or so.

You can use the Refresh icon to update the status in the view.

__2. Confirm that the build is successful.

__a. When it completes, double-click the build to open the result editor.

__b. Note that the build is complete and green.



117/176

IBM Software

__3. Tag the build as ready for test.

__a. Place the cursor in theTags field and press Ctrl+Space to open the list of availabletags. Select ready_for_test from the list.

__b. ClickSave on the build result.

__4. Return to the work item editor for theSurfer squawker story, select Set Implemented and thenclick Save. This sets the status to Implemented. This, in addition to the work items listed asincluded in the build, indicates to the test team what is ready for testing.

__5. Close the Rational Team Concert window.



118/176

IBM Software

4.4 Monitor Build Status

Team role

You are performing the role of Tanuj, the test lead. In this section, youwill use the SquawkQM Web UI to monitor the build status.

__1. Log into the SquawkQM Web UI as Tanuj. You may already be logged in from earlier. If not:

__a. In the Windows taskbar, clickTools RQM IBM Rational Quality Manager

__b. EnterTanuj for both the User ID and Password, and then click Log In.



119/176


120/176

IBM Software

__3. Click the top entry with the right mouse button and select the Open Link in New Tab action.

__a. If prompted, log in as Tanuj.

__b. Explore the build result. Look at what JUnit tests were executed, what download(s) werecreated, the contents of the log file, etc.

Deployment of Build

The build script used to create the Squawker application (by Debearlier) also contains tasks that deploy the application to the testserver, if the build completes successfully. The application is

deployed to the test server, which Tanuj will access in future steps.



121/176

IBM Software


__c. Lets verify that the build that was deployed is actually the one on the test server.

__i. Open Windows Explorer from the icon in the Quick Launch bar, and navigate tothe C:\CALMData\Testing directory.

__ii. Double-click theBuildInfo.txt file to open it.

__iii. Verify that theBuild label information in that file matches the build result you justrecently explored above. In the build result above, the label is I20090627-1110.

__d. Log out of Rational Quality Manager and close the browser window. Close WindowsExplorer, the text editor, and Rational Team Concert.

Conclusion

This concludes the lab. The high priority surfer squawkerrequirement has been implemented (or has it?) and the build hasbeen delivered to the test team. Next you will see how Collaborative

Application Lifecycle Management (C/ALM) streamlines testing andfixing bugs.


122/176

IBM Software

Lab 5 Respond to a Test Failure

Hopefully by now youve had the unique opportunity to play the game whack-a-mole. Its kind of likefinding and fixing defects, wouldnt you say? Upon defect discovery, a tester logs a defect reportincluding a detailed set of steps needed to recreate the defect. In turn, the developers cant recreate the

defect. Despite efforts to improve defect reports and reproducibility it remains a challenge that createsmore friction than lean, mean software delivery machines need.

When a tester executes a test, the results are captured by Rational Quality Manager, which is veryimportant information to the testers. But the key question is how can you share it with the developerswhen reporting defects? Next youll see why finding and fixing a defect doesnt have to feel like playingwhack-a-mole.

In this lab, you will correct the mistake you made as Deb in the previous lab. As Tanuj, you are going todiscover the mistake and you will explore this crucial part of the application lifecycle.

Tanuj needs insight into:

Build status: when is the build ready for test?

Build clarity: what is implemented in the build?

Build quality: what build verification tests were run and with what result?

Marco needs insight into:

Defects blocking test



123/176

IBM Software

Deb needs insight into:

The test case that failed (steps to recreate defect)

The test environment it ran on (include pointer to the physical/virtual machine)

The build ID used by test

5.1 Execute Test and Submit Defect

Team role

You are performing the role of Tanuj, the test lead. In this section, youwill use the SquawkQM Web UI and Rational Quality Manager tool toexecute test and submit a defect.

__1. Log into the Rational Quality Manager Web UI as Tanuj

__a. Switch back to the Rational Quality Manager tab in your browser. If you have closedRational Quality Manager, follow these steps to log in as Tanuj.

__b. In the Windows taskbar, clickTools RQM IBM Rational Quality Manager.

Lab 5 Respond to a Test Failure Page 121


124/176

IBM Software

__i. EnterTanuj for both the User ID and Password, and then press Log In.



125/176

IBM Software

__2. Run the Surfer test from the test execution record

__a. SelectView Test Execution Records from the Execution menu at the top of the Webpage.



126/176

IBM Software

__b. Make sure that the list is sorted by Last Modified descending as shown. Check the boxnext to GUISurfer_Windows test execution record. Make sure that the Test Script is setto GUI Surfer

__c. Click theRun icon at the top right of the list.



127/176

IBM Software

__d. Read and perform steps 1 through 4. As you complete each step or substep, click the

Pass icon to mark the step as a Pass.



128/176


129/176

IBM Software

__3. Capture a screen image of the failure

__a. Select theSquawk window and press Alt-PrtSc on your keyboard to capture an imageof the application.

__b. Open the WindowsPaint application from the desktop.

__c. In Paint, use theEdit Paste menu to paste the image.



130/176

IBM Soft

pot.rational.09.2.066.01 workbook

Documents