Your SlideShare is downloading. ×
Best practices   quality assurance
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Best practices quality assurance

3,337
views

Published on


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

  • Be the first to like this

No Downloads
Views
Total Views
3,337
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
31
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Shakal Shukla
  • 2.
    • Who must have commitment to deliver a Quality Software to the Customer ?
  • 3. What is Quality
    • Quality Deliverables within time ?
    • Bug Free software ?
    • Customer Satisfaction ?
    • Quality Deliverables within budget ?
  • 4. What is Error ?
    • What is an error?
    • - Unexpected result – [Swapnil]
    • - Mistake – Unplanned human action that produces an incorrect result.
    • - Fault / Failure / Error / Issue / Bug
  • 5. Why software have a bugs?
    • Miscommunication or No communication
    • Software Complexity
    • Programming errors
    • Changing Requirements
    • Time pressures / Unrealistic schedule
    • Egos
    • Poor documentation
  • 6. 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.
  • 7. Other Factors..
    • Performance of application
    • Security of application
    • Memory leakages
  • 8. Questions to QA..
    • QA are paid for breaking software or Developer ? 
    • What QA should pursue ?
      • Error Or Developer
  • 9. Keywords..
    • QA pursue errors not people.
    • QA breaks software because QA cares.
  • 10. Goal of QA
    • Standard Goal ..
    • Find issues
    • Find it ASAP
    • Get it fix
    • Practical Goal ..
    • No issues from customer within 2-3 hours after delivery/release.
  • 11. 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
  • 12. Do’s for QA
    • Result Analysis
    • Issue Log
    • Verification of Issues
    • Regression testing
    • Automation
  • 13. 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
  • 14. Understanding of Requirement
    • Read thoroughly
    • Create points or notes / Summary
    • Use tools – Mind Maps
    • Read / Discuss / Explore
  • 15. 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
  • 16. Testing Approach
    • 4 W – 1 H Concept
      • What
      • Who
      • When
      • Where
      • How
    • UI – Functional – Integration/Impact
    • +ve testing first & then –ve testing.
  • 17. Other testing
    • Performance
    • Load
    • Stress
    • Security
    • Compatibility
    • Mutation
  • 18. Result Analysis..
    • Before logging issue..
    • Confirm functionality.
    • Confirm spellings
    • Confirm User interface - Alignment
    • Confirm impact
  • 19. 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
  • 20. 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.
  • 21. Issue log
    • Use tools
    • References
    • Screen shots
      • Properly maintained on location
      • Less size
      • Mentioning of screen shot
      • Highlight issue in screen shot
    • Reduce duplicates
  • 22. Important points
    • Peer Reviews
    • Quality standards
    • Ideal Process
  • 23. 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.
  • 24.