Qa process 2012
11
QA Process
-
Upload
ashokack -
Category
Technology
-
view
542 -
download
2
description
RC QA Process
Transcript of Qa process 2012
QA Process
QA Responsibility
QA is responsible for making their decision on what to test includes test cases, test types and test scenarios
Prioritization of the work should be discussed BAs.
All non-verbal communication should include Bas
Attend daily stand-ups, QA Walkthrough as directed in sprint planning
Test Case
Test case for a bug, enhancement or a new report should be created and reviewed by BA and Developer
Test cases can be stored in Jira, QC, Excel or any other tools.
Test cases will be attached to the Jira issues for tracking purpose.
Types of Testing
• Functional– To make sure the tests are executed against test case, new reports,
first time reported defects• Regression
– Existing reports where test cases already documented.• Exploratory
– Test case documentation is not necessary, testing is conducted to explore the breadth coverage of the functionality
• Automation– Existing regression test cases will be automated to reduce the manual
testing ( 2012 plan to increase the scope of automation in SR)• Smoke
– Execute a small subset of P1 or happy test cases
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 4
Good examples of test execution
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 5
Sample Test Result :
I have completed the QA test execution for PSSR-21375. There were a total of 37 test cases, with 27 pass results and 10 fail results on PS 7.1.0. The fail results are discussed in further detail below. The test cases and results are in the attached spreadsheet. Feel free to contact me if you have any questions or comments. Thanks!All of the fail results encountered during testing were due to the same issue. When the NJ School Attendance Report is run using the Current School Only option, no students are extracted. Test cases effected - 12, 13, 14, 15, 16, 27, 28, 29, 30, 31.
Defect reporting
• Auto fill description field with a template. This helps defect writing and provides consistency on defect reported
– http://confluence.powerschool.com/display/QA/AutoFill+Description+Field+for+Jira+-+Using+JavaScript
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 6
Test Environment
• Every QA should have there own dedicated environment.• At least 2 Test environment/QA is available • For the environment process. Refer to the process described here• http://confluence.powerschool.com/display/QA/Quality+Assurance
+Environments• Browser coverage
Internet Explorer 8 and 9 Firefox 3.6 and 4 Safari 4 and 5
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 7
Environment allocation
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 8
QA Walkthrough
• Goal: Increase the quality of software after DEVQUAL is complete, but prior to the actual build being created, and then deployed to "sandbox".
– Create walkthrough subtask with estimate– Engineer calls for walkthrough– Walkthrough occurs and QA provides feedback – No Jira tickets (except items not to be fixed in sprint.)QW Jira ticket updated with actual time
spent, and notes from QA analyst Engineers agree to whether or not to close walkthrough subtask, and build.
• Walkthrough is NOT an execution of the full suite of tests that the QA organization intends to execute.....think of it as something between a smoke test and exploratory testing.
http://confluence.powerschool.com/display/QA/Quality+Walkthrough+Process
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 9
QA buddies
• QA buddies from Core as been assigned for subject expertise and knowledge share– http://confluence.powerschool.com/display/SR/QA+buddies
Copyright © 2010 Pearson Education, Inc. or its affiliates. All rights reserved. 10
