® ibm software group © 2009 ibm corporationibm confidential rational team concert 2.0.0.1 svt team...

®

IBM Software Group

© 2009 IBM CorporationIBM Confidential

Rational Team Concert 2.0.0.1 SVT Team Meeting – 08/12/2009

IBM Software Group | Rational software

2

IBM Confidential

Agenda

Info

Where are we?

Cindy’s Thoughts

Test Execution – What’s due?

Test Execution Process

Questions


3

IBM Confidential

Info

Build to start testing with: IM link for the build:

http://apollobuildserv12.ottawa.ibm.com:8080/integration/rtc.200x.integration/I20090811-1601/install-repository/standard/

Smoketests were not completed (RES shutdown the machine)

Sachin’s team successfully installed the build

Sujana will work with the build and send out mail

Build info is being tracked in Workitem: 89604

Do not use 0809-1600 due to Workitem: 89717

Cindy is out on vacation next week (8/17- 8/21)

Karen is out on 8/17 and 8/18


4

IBM Confidential

Where are we?

Almost Finished Planning

Just have the finishing touches around Integrations to do

CTP has been sent out for review. We are receiving comments.

We are in Test Execution now


5

IBM Confidential

Cindy’s Thoughts about Test Execution

Keep to the schedule Test Execution needs to be done by 9/4

Set weekly goals for test execution – and keep to them!

We do NOT want to work over Labor Day (USA holiday) weekend (9/5-9/7)

Timely communication Update your points in RQM TERs – DAILY

File all defects found that day – by the end of the day

Escalate issues to Karen and Cindy – immediately

Set aside around 45 minutes at the end of the day to complete your “end of day” tasks


6

IBM Confidential

Test Execution – What’s due?

By the end of day Thursday (8/13)

– Send Karen the Test Execution Status slide

By the end of the week (8/14)

– Assessment report drafts for each Scenario

– ALL test prep tasks completed


7

IBM Confidential

Assessment Report – Detailed SVT Results

Fill in Scenario Goal and Customer Expectations in the Assessment_Report_Detailed_Results_Template.doc Will be sent after this meeting

Naming convention for file: <scenario prefix>_Assessment_Detailed_Results_<version number>.doc

Example: eds_Assessment_Detailed_Results_1.doc

Send to Karen by 8/14


8

IBM Confidential

Test Execution Process

RQM – Tracking test execution

Filing defects in RTC (jazz.net)

Keep Assessment report notes


9

IBM Confidential

RQM Dashboard – Create Test Execution by Schedule

Steps:

Create a New Tab

Scroll to Quality Manager

Select Execution by Test Schedule

Next Step:

Click to Add Viewlet


10

IBM Confidential

RQM Dashboard – Create Test Execution by Schedule (con’t)

Next Steps:

Select your 2.0.0.1 Test Plan from dropdown menu

Select the correct Test Milestone – SVT_2.0.0.1

Select ALL Test Case

Select ALL Owner

Select ALL State

Save

Click + to Expand to see entire Schedule with Points distribution


11

IBM Confidential

Filing Defects

How Found field is ‘Test’

These are the guidelines for submitting defects in RTC for 2.0.0.1. Note - 3 new attributes have been added to the work item type 'Defect' - How Found, OS and Client. Select from the dropdown for each one when submitting a new defect.

Tags will be used in addition to How Found to identify that the defect was submitted by SVT. This is a very important step - ALL DEFECTS MUST HAVE HOW FOUND - 'TEST' AND A TAG. The only valid tags to use are svt and svt_spt (unless defect has consumability impact)


12

IBM Confidential

Consumability Reminder for Defects

Enter Consumability Defects with tags:

Tags created for each category in RTC and JF repositories:

svt_cons_edb (Ease of Doing Business)

svt_cons_pfu (Positive First Use)

svt_cons_ric (Rapid Integration into Customers Environment)

svt_cons_rac (Readily Adapts to Customer Requirements)

svt_cons_soo (Simplifies Ownership and Operation)


13

IBM Confidential

Questions?

® ibm software group © 2009 ibm corporationibm confidential rational team concert 2.0.0.1 svt team...

Documents