Testing is not just enough! 10 things that you need to do beyond it.

Software testing always a never ending job! has no limits. in all situation, software testing asks, “How do I know if I’m doing, or have done enough of the right type of testing?” Unfortunately, there is no objective or rigorous calculus for answering this question, but we can identify what to consider in attempting to answer it. 

Testing job is not just to ensure that functionalities are working or not or executing regression testing and updating results. Looking product from different perspectives and understanding end user requirements in different scenarios make the whole lot of difference. We can do beyond testing to be at par with quality standards.

Let’s understand what is required beyond regular testing.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Software testing always a never ending job! has no limits. in all situation, software testing asks, “How do I know if I’m doing, or have done enough of the right type of testing?” Unfortunately, there is no objective or rigorous calculus for answering this question, but we can identify what to consider in attempting to answer it. 

Testing job is not just to ensure that functionalities are working or not or executing regression testing and updating results. Looking product from different perspectives and understanding end user requirements in different scenarios make the whole lot of difference. We can do beyond testing to be at par with quality standards.

Let’s understand what is required beyond regular testing.

  1. Competitive study – Understand market needs
  2. Technical sessions – Share knowledge and take inputs from stake holders
  3. Detailed Test Strategy – Document your understanding and approach
  4. Peer to peer reviews – Involve team members in reviews
  5. Automation for Smoke, Regression, Performance,24X7 tests
  6. Code coverage – understand depth of your tests
  7. Feature Workshops – Form an internal Users group to evaluate your feature
  8. Publish feature white paper on customer/public forums
  9. Early drop of feature to customers -Know your customer pulse
  10. Replicate customer environments at your test labs

Learning Outcome

"Quality is never an accident; it is always the result of doing different things to achieve the quality and customer satisfaction.". This session propagates different ideas for quality improvement of your product.

Target Audience

QA Engineers

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal