best practices quality assurance
DESCRIPTION
TRANSCRIPT
![Page 1: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/1.jpg)
Shakal Shukla
![Page 2: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/2.jpg)
Who must have commitment to deliver a Quality Software to the Customer ?
![Page 3: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/3.jpg)
What is Quality
Quality Deliverables within time ? Bug Free software ? Customer Satisfaction ? Quality Deliverables within budget ?
![Page 4: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/4.jpg)
What is Error ?
What is an error? - Unexpected result – [Swapnil]
- Mistake – Unplanned human action that produces an incorrect result.
- Fault / Failure / Error / Issue / Bug
![Page 5: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/5.jpg)
Why software have a bugs? Miscommunication or No communication
Software Complexity
Programming errors
Changing Requirements
Time pressures / Unrealistic schedule
Egos
Poor documentation
![Page 6: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/6.jpg)
Developer approach
Requirement gathering / Study. Best practices / Coding standards. Proper commenting. Unit Testing. Creative User Interface. Basic validations. Systematic approach while fixing issues. Comments in issue log.
![Page 7: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/7.jpg)
Other Factors..
Performance of application
Security of application
Memory leakages
![Page 8: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/8.jpg)
Questions to QA..
QA are paid for breaking software or Developer ?
What QA should pursue ? Error Or Developer
![Page 9: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/9.jpg)
Keywords..
QA pursue errors not people.
QA breaks software because QA cares.
![Page 10: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/10.jpg)
Goal of QAStandard Goal ..
Find issues Find it ASAP Get it fix
Practical Goal ..
• No issues from customer within 2-3 hours after delivery/release.
![Page 11: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/11.jpg)
Do’s for QA..
Proper understanding of requirement. Discussion with Leads & Developer. Test Plan Review & Approve plan from Lead Test Cases Review & Approve cases from Lead Test Environment Test cases execution – Testing
![Page 12: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/12.jpg)
Do’s for QA
Result Analysis Issue Log Verification of Issues Regression testing Automation
![Page 13: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/13.jpg)
Don'ts for QA Understanding functionality & then write
test cases. Positive testing & then Negative testing Give enough time to developer Suggestion to Developer on tech front. Unorganized or Adhoc approch
![Page 14: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/14.jpg)
Understanding of Requirement Read thoroughly
Create points or notes / Summary
Use tools – Mind Maps
Read / Discuss / Explore
![Page 15: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/15.jpg)
Test Cases What is a use of Test cases ? Test Pre-requisites Language used Priority Mapping of Expected result & Actual
result. Use Tools – Test Director Redundancy Sequence of test cases
![Page 16: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/16.jpg)
Testing Approach
4 W – 1 H Concept What Who When Where How
UI – Functional – Integration/Impact +ve testing first & then –ve testing.
![Page 17: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/17.jpg)
Other testing
Performance Load Stress Security Compatibility Mutation
![Page 18: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/18.jpg)
Result Analysis..Before logging issue..
Confirm functionality. Confirm spellings Confirm User interface -
Alignment Confirm impact
![Page 19: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/19.jpg)
Issue log Proper language
Polite words should be used ( like need to be …)
Proper summary Wrong functionality (Is this sentence is
meaningful ?) Set proper Severity & Priority Steps to reproduce Pre-requisites Maintain each & every issue for proper
track issue
![Page 20: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/20.jpg)
Issue log Issue status Proper comments from developer High severity/priority issue is “Not an
issue” – poor understanding of functionality.
Maintain History of sever bugs Follow up of bugs Issue should not be orally logged. Issue count is not important.
![Page 21: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/21.jpg)
Issue log Use tools References Screen shots
Properly maintained on locationLess sizeMentioning of screen shotHighlight issue in screen shot
Reduce duplicates
![Page 22: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/22.jpg)
Important points
Peer Reviews Quality standards Ideal Process
![Page 23: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/23.jpg)
Last word…
All though QA and developer both runs to achieve qualities, but the only problem is they do it by their own way.
Both should complement each other.
![Page 24: Best practices quality assurance](https://reader033.vdocuments.us/reader033/viewer/2022061118/54692643af79596a1b8b64db/html5/thumbnails/24.jpg)