SlideShare a Scribd company logo
1 of 21
Page 1 Medicity Proprietary & Confidential
R&D Lunch and Learn
Testing Overview
Internal Use Only
By Kaylene
7/29/2015
or - “Bug Hunting for Beginners”
Page 2 Medicity Proprietary & Confidential
Darling…get up
quickly…there
seems to be a
BUG in your bed!
What is the
severity?
Please log it in
Rally.
Page 3 Medicity Proprietary & Confidential
Introduction
Page 4 Medicity Proprietary & Confidential
1. Purpose of Testing
2.Traits of a Good Tester
3. Test Design
4. The Test Case
5. Testing
6. Questions and Answers
Course Content
Page 5 Medicity Proprietary & Confidential
1. Purpose
of
Testing
Page 6 Medicity Proprietary & Confidential
1. The Purpose of Testing
• To Find Bugs
• To Provide a Level of Assurance to the
Customer
Page 7 Medicity Proprietary & Confidential
2. Traits of
A Good Tester
Page 8 Medicity Proprietary & Confidential
2. Traits of a Good Tester
• Curiosity
• Persistence
• Creativity
• Able to cope under pressure
• Consistency
Page 9 Medicity Proprietary & Confidential
3. Test Design
Page 10 Medicity Proprietary & Confidential
3. Test Design – Testing Document
Testing Objective Document:
- Overview of User Story
- Assumptions
- Out of Scope Items
- Notes
- Risks and Mitigation
- Dependencies
- Acceptance Criterias
- Testing Objectives
- Approvals
Test Plan and Objectives Document:
- Customer Environment
- Product Setup
- Release Items
- Risks and Mitigation
- Assumptions
- Test Plan: Feature Item,
Objective, Test Set Name
- Retrospective and Approvals
Page 11 Medicity Proprietary & Confidential
Page 12 Medicity Proprietary & Confidential
4. The Test Case
Page 13 Medicity Proprietary & Confidential
4. The Test Case
TESTS
Some Areas of a Test Case
•Test Case Name
•Description
•Attachments
•Test Folder
•Test Case Objective
•Work Product
•Type
•Method
•Pre-Conditions
•Test Steps – Input & Expected Result
•Post-Conditions
•Notes
- It validates the test objective
- It has a reasonable probability of
catching an error
- It is not redundant
Characteristics of a good test satisfy the following criteria:
Page 14 Medicity Proprietary & Confidential
5. Testing
a. Testing
b. Test Methods
c. Quiz - Examples
Page 15 Medicity Proprietary & Confidential
5a.Testing
Test Type What When Who
Acceptance Validation Testing Sprints QA
Hardening Full Feature Testing Last
Sprint-
week 1
Team
Regression Package to customer
works, integration test
Last
Sprint-
week 2
Team
Page 16 Medicity Proprietary & Confidential
No single technique is the best technique
Positive Testing
Acceptance Validation
Regression Testing
Negative Testing
5b Test Types/Methods
Functional Testing
Boundary Analysis
Performance Testing
Usability Testing
Page 17 Medicity Proprietary & Confidential
5c-1: Example
Positive and Negative Testing
Requirement: Develop field for the user to enter in their age.
?
?
Page 18 Medicity Proprietary & Confidential
5c-2: Example
Boundary Analysis
1-120
0 and 121
?
?
Requirement: Develop field for the user to enter in their age.
Design: Mandatory field that allows for entry of numeric value
between and including: 1 and 120.
Page 19 Medicity Proprietary & Confidential
Failure is informative, not terminal.
Page 20 Medicity Proprietary & Confidential
Fewer Bugs makes everyone happy!!
Page 21 Medicity Proprietary & Confidential
6. Questions and Comments

More Related Content

Similar to LunchAndLearnBugHuntingForBeginners07292015

Anton Muzhailo - Practical Test Process Improvement using ISTQB
Anton Muzhailo - Practical Test Process Improvement using ISTQBAnton Muzhailo - Practical Test Process Improvement using ISTQB
Anton Muzhailo - Practical Test Process Improvement using ISTQBIevgenii Katsan
 
Istqb question-paper-dump-7
Istqb question-paper-dump-7Istqb question-paper-dump-7
Istqb question-paper-dump-7TestingGeeks
 
Claudiu Draghia ITEM 2018
Claudiu Draghia ITEM 2018Claudiu Draghia ITEM 2018
Claudiu Draghia ITEM 2018ITEM
 
Introducing QA Into an Agile Environment
Introducing QA Into an Agile EnvironmentIntroducing QA Into an Agile Environment
Introducing QA Into an Agile EnvironmentJoseph Beale
 
Testing the unknown: the art and science of working with hypothesis
Testing the unknown: the art and science of working with hypothesisTesting the unknown: the art and science of working with hypothesis
Testing the unknown: the art and science of working with hypothesisArdita Karaj
 
WCM 2012 5 Ways to Reduce Warranty Costs
WCM 2012 5 Ways to Reduce Warranty CostsWCM 2012 5 Ways to Reduce Warranty Costs
WCM 2012 5 Ways to Reduce Warranty CostsAccendo Reliability
 
Continuous discovery - Caitlin Blackwell
Continuous discovery - Caitlin BlackwellContinuous discovery - Caitlin Blackwell
Continuous discovery - Caitlin BlackwellProduct Anonymous
 
Life of a pragmatic tester
Life of a pragmatic testerLife of a pragmatic tester
Life of a pragmatic testerGitte Ottosen
 
10 signs your testing is not enough
10 signs your testing is not enough10 signs your testing is not enough
10 signs your testing is not enoughSQALab
 
Test Execution
Test ExecutionTest Execution
Test ExecutionRajathi-QA
 
IT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGIT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGSathya R
 
Test Driven Development – how it benefits business and teams alike
Test Driven Development – how it benefits business and teams alikeTest Driven Development – how it benefits business and teams alike
Test Driven Development – how it benefits business and teams alikeScrum Australia Pty Ltd
 
Private Label Sourcing from China -- Best Practices
Private Label Sourcing from China -- Best Practices Private Label Sourcing from China -- Best Practices
Private Label Sourcing from China -- Best Practices Global Sources
 
Test management struggles and challenges in SDLC
Test management struggles and challenges in SDLCTest management struggles and challenges in SDLC
Test management struggles and challenges in SDLCFumikazu FUJIWARA
 
Agile testing - Madhu Krishnappa
Agile testing - Madhu KrishnappaAgile testing - Madhu Krishnappa
Agile testing - Madhu KrishnappaPiyush Rahate
 
Lect.2-what is QC -QA_R.pdf
Lect.2-what is QC -QA_R.pdfLect.2-what is QC -QA_R.pdf
Lect.2-what is QC -QA_R.pdfZaryabAhmad13
 
Model Governance and Validation: Best Practices and Common Pitfalls
Model Governance and Validation: Best Practices and Common PitfallsModel Governance and Validation: Best Practices and Common Pitfalls
Model Governance and Validation: Best Practices and Common PitfallsMarkSpong1
 
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don Peters
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don PetersMHA2018 - Quality Advocacy: The next progression for Agile Testers - Don Peters
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don PetersAgileDenver
 

Similar to LunchAndLearnBugHuntingForBeginners07292015 (20)

Anton Muzhailo - Practical Test Process Improvement using ISTQB
Anton Muzhailo - Practical Test Process Improvement using ISTQBAnton Muzhailo - Practical Test Process Improvement using ISTQB
Anton Muzhailo - Practical Test Process Improvement using ISTQB
 
Istqb question-paper-dump-7
Istqb question-paper-dump-7Istqb question-paper-dump-7
Istqb question-paper-dump-7
 
Claudiu Draghia ITEM 2018
Claudiu Draghia ITEM 2018Claudiu Draghia ITEM 2018
Claudiu Draghia ITEM 2018
 
Introducing QA Into an Agile Environment
Introducing QA Into an Agile EnvironmentIntroducing QA Into an Agile Environment
Introducing QA Into an Agile Environment
 
Testing the unknown: the art and science of working with hypothesis
Testing the unknown: the art and science of working with hypothesisTesting the unknown: the art and science of working with hypothesis
Testing the unknown: the art and science of working with hypothesis
 
WCM 2012 5 Ways to Reduce Warranty Costs
WCM 2012 5 Ways to Reduce Warranty CostsWCM 2012 5 Ways to Reduce Warranty Costs
WCM 2012 5 Ways to Reduce Warranty Costs
 
Continuous discovery - Caitlin Blackwell
Continuous discovery - Caitlin BlackwellContinuous discovery - Caitlin Blackwell
Continuous discovery - Caitlin Blackwell
 
Life of a pragmatic tester
Life of a pragmatic testerLife of a pragmatic tester
Life of a pragmatic tester
 
10 signs your testing is not enough
10 signs your testing is not enough10 signs your testing is not enough
10 signs your testing is not enough
 
Test Execution
Test ExecutionTest Execution
Test Execution
 
IT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGIT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTING
 
Test Driven Development – how it benefits business and teams alike
Test Driven Development – how it benefits business and teams alikeTest Driven Development – how it benefits business and teams alike
Test Driven Development – how it benefits business and teams alike
 
How To Improve Your Product Testing Program
How To Improve Your Product Testing ProgramHow To Improve Your Product Testing Program
How To Improve Your Product Testing Program
 
Private Label Sourcing from China -- Best Practices
Private Label Sourcing from China -- Best Practices Private Label Sourcing from China -- Best Practices
Private Label Sourcing from China -- Best Practices
 
Test management struggles and challenges in SDLC
Test management struggles and challenges in SDLCTest management struggles and challenges in SDLC
Test management struggles and challenges in SDLC
 
Agile testing - Madhu Krishnappa
Agile testing - Madhu KrishnappaAgile testing - Madhu Krishnappa
Agile testing - Madhu Krishnappa
 
Agile testing
Agile testingAgile testing
Agile testing
 
Lect.2-what is QC -QA_R.pdf
Lect.2-what is QC -QA_R.pdfLect.2-what is QC -QA_R.pdf
Lect.2-what is QC -QA_R.pdf
 
Model Governance and Validation: Best Practices and Common Pitfalls
Model Governance and Validation: Best Practices and Common PitfallsModel Governance and Validation: Best Practices and Common Pitfalls
Model Governance and Validation: Best Practices and Common Pitfalls
 
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don Peters
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don PetersMHA2018 - Quality Advocacy: The next progression for Agile Testers - Don Peters
MHA2018 - Quality Advocacy: The next progression for Agile Testers - Don Peters
 

More from Kaylene Arambula CSQE, CQIA, SMC (6)

ICP-ATA
ICP-ATAICP-ATA
ICP-ATA
 
ICP-IGAgile Certified Professional
ICP-IGAgile Certified ProfessionalICP-IGAgile Certified Professional
ICP-IGAgile Certified Professional
 
Diploma
DiplomaDiploma
Diploma
 
ICP-ATA
ICP-ATAICP-ATA
ICP-ATA
 
CQIA
CQIACQIA
CQIA
 
Kaylene Arambula
Kaylene ArambulaKaylene Arambula
Kaylene Arambula
 

LunchAndLearnBugHuntingForBeginners07292015

  • 1. Page 1 Medicity Proprietary & Confidential R&D Lunch and Learn Testing Overview Internal Use Only By Kaylene 7/29/2015 or - “Bug Hunting for Beginners”
  • 2. Page 2 Medicity Proprietary & Confidential Darling…get up quickly…there seems to be a BUG in your bed! What is the severity? Please log it in Rally.
  • 3. Page 3 Medicity Proprietary & Confidential Introduction
  • 4. Page 4 Medicity Proprietary & Confidential 1. Purpose of Testing 2.Traits of a Good Tester 3. Test Design 4. The Test Case 5. Testing 6. Questions and Answers Course Content
  • 5. Page 5 Medicity Proprietary & Confidential 1. Purpose of Testing
  • 6. Page 6 Medicity Proprietary & Confidential 1. The Purpose of Testing • To Find Bugs • To Provide a Level of Assurance to the Customer
  • 7. Page 7 Medicity Proprietary & Confidential 2. Traits of A Good Tester
  • 8. Page 8 Medicity Proprietary & Confidential 2. Traits of a Good Tester • Curiosity • Persistence • Creativity • Able to cope under pressure • Consistency
  • 9. Page 9 Medicity Proprietary & Confidential 3. Test Design
  • 10. Page 10 Medicity Proprietary & Confidential 3. Test Design – Testing Document Testing Objective Document: - Overview of User Story - Assumptions - Out of Scope Items - Notes - Risks and Mitigation - Dependencies - Acceptance Criterias - Testing Objectives - Approvals Test Plan and Objectives Document: - Customer Environment - Product Setup - Release Items - Risks and Mitigation - Assumptions - Test Plan: Feature Item, Objective, Test Set Name - Retrospective and Approvals
  • 11. Page 11 Medicity Proprietary & Confidential
  • 12. Page 12 Medicity Proprietary & Confidential 4. The Test Case
  • 13. Page 13 Medicity Proprietary & Confidential 4. The Test Case TESTS Some Areas of a Test Case •Test Case Name •Description •Attachments •Test Folder •Test Case Objective •Work Product •Type •Method •Pre-Conditions •Test Steps – Input & Expected Result •Post-Conditions •Notes - It validates the test objective - It has a reasonable probability of catching an error - It is not redundant Characteristics of a good test satisfy the following criteria:
  • 14. Page 14 Medicity Proprietary & Confidential 5. Testing a. Testing b. Test Methods c. Quiz - Examples
  • 15. Page 15 Medicity Proprietary & Confidential 5a.Testing Test Type What When Who Acceptance Validation Testing Sprints QA Hardening Full Feature Testing Last Sprint- week 1 Team Regression Package to customer works, integration test Last Sprint- week 2 Team
  • 16. Page 16 Medicity Proprietary & Confidential No single technique is the best technique Positive Testing Acceptance Validation Regression Testing Negative Testing 5b Test Types/Methods Functional Testing Boundary Analysis Performance Testing Usability Testing
  • 17. Page 17 Medicity Proprietary & Confidential 5c-1: Example Positive and Negative Testing Requirement: Develop field for the user to enter in their age. ? ?
  • 18. Page 18 Medicity Proprietary & Confidential 5c-2: Example Boundary Analysis 1-120 0 and 121 ? ? Requirement: Develop field for the user to enter in their age. Design: Mandatory field that allows for entry of numeric value between and including: 1 and 120.
  • 19. Page 19 Medicity Proprietary & Confidential Failure is informative, not terminal.
  • 20. Page 20 Medicity Proprietary & Confidential Fewer Bugs makes everyone happy!!
  • 21. Page 21 Medicity Proprietary & Confidential 6. Questions and Comments

Editor's Notes

  1. Executing Test Sets   While executing test sets, assign your name as owner.   Test Sets that have been created and either do not have any TCs associated to them and they are accepted.  If they were not run then please delete them from the Sprint by either using the delete or changing the iteration if you do not want to lose them.   In addition, I am also seeing a number of TSs that contain TCs that were not executed. If you are not going to execute the TC then please delete it from the TS. If you cannot execute the test case due to a known defect or a blocker then result appropriately.   When a TS is marked accepted it means that everything contained has been executed (or noted) regardless of pass/fail. When the TC fails do not mark both instances as failed. You wait for the fix and test it again. You keep adding the TC to the iteration until it passes and then once more to be tested in a subsequent build.