Best practices quality assurance

6,635 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,635
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
66
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Best practices quality assurance

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

×