Introduction to Software Testing

I am happy to announce Introduction to Testing series which helps students and freshers in IT industry to mark their career in Software Testing.

A critical element in the successful development of any software application is effective testing.  Testing moves the evolution of a product from a state of hypothetical usefulness to proven usefulness. It includes the testing of requirements, design, systems’ code, documentation, and operational procedures; and is an inseparable part of the development of a product which the purchaser and end-user view as beneficial and meeting their needs.  Testing is one of the ways in which a product achieves high quality.

What is testing?

Is context based, risk driven methodical and disciplined approach to finding bugs, reporting bugs to the developer for fixing followed by retesting and conformtion.  

Testing is the systematic search for defects in all project deliverables.  It is the process of examining an output of a process under consideration, comparing the results against a set of pre-determined expectations, and dealing with the variances.

Testing will take on many forms.  As the form and content of the output change, the approaches and techniques used to test them must be adapted.

Testing is a process of verifying and/or validating an output against a set of expectations and observing the variances.

Fundamentals of Testing

Testing is conducted to ensure that you develop a product that will prove to be useful to the end user.  The primary objectives of testing assure that:

  • The system meets the users’ needs … has ‘the right system been built’
  • The user requirements are built as specified … has ‘the system been built right’

Other secondary objectives of testing are to:

  • Instill confidence in the system, through user involvement
  • Ensure the system will work from both a functional and performance viewpoint
  • Ensure that the interfaces between systems work
  • Establish exactly what the system does (and does not do) so that the user does not receive any “surprises” at implementation time
  • Identify problem areas where the system deliverables do not meet the agreed to specifications
  • Improve the development processes that cause errors.

Achieving these objectives will ensure that:

  • The associated risks of failing to successfully deliver an acceptable product are minimized,
  • A high quality product (as the application purchaser and user view it) is delivered, and
  • The ability to deliver high quality applications is improved.

The purpose of a testing method is to provide a framework and a set of disciplines and approaches for testing of a software application, so that the process is consistent and repeatable.


Thanks for visiting QAInsights! Check out our new portal to get updates on Software Testing related certifications. We’re always posting interesting articles on QAInsights. I request you to subscribe so you don’t miss out anything.

Searching for QA Jobs Openings, check it at

Subscribe to our QAInsights YouTube Channel. Subscribe our free weekly newsletter or Google feeds

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Join the fastest growing Performance Engineers club at ClubhouseSHOW ME HOW
+ +
Share via
Copy link