All IT Courses 50% Off
QA Tutorials

Exception / Error Handling in Software Testing

The large scale software is too complex to be bug free; no matter how much testing we do. We cannot test for all the different ways our users are interacting with our application. It is important for us to understand the difference between errors and exceptions in any applications and the correct ways to handle manage them so that we can take a proactive approach to maintaining a healthy application for both your development team and our end users.

The Limitations of Testing:

Even with the most detail testing process, we are still only testing specific situations and have our own bias that comes into play. Suddenly thousands of users are using your system, not even thought of. They will almost certainly run into something you didn’t tested.

What is the differences between Errors and Exceptions


Programming errors are those where there’s no chance to recover or continue gracefully and typically need programmer to return and alter the code to fix it. Errors can be turned into exceptions so that they can be handled within the code. Errors can usually be avoided with simple checks and if simple checks won’t suffice errors can also turn into exceptions so that applications can handle the situations gracefully.


Take advantage of language-specific semantics and present when something exceptional has happened. Exceptions are thrown and caught therefore the code can recover and handle the situations and not enter a mistake state. This also lets the application can recover or continue. Where unhandled exceptions can also be logged so they are looked at by developer to fix the underlying error.

Error handling testing is a type of software testing that is done to check whether the system is capable of or able to handle errors that may happen in future. This type of testing is done with the help of both developers and testers. Error handling testing not only focuses on the determination of error but also focuses on the exception handling. 

Objectives of Error Handling Testing:

  • It checks the system ability to handle errors. 
  • It checks the system highest soak point
  • To make sure errors can be well managed by the system in the future.
  • The system is capable of exception handling also.

The different steps in error handling are:
  1. Test environment setup- Test environment is set based on the software testing technique so that the testing process can run smoothly. This step includes planning for testing. System will be tested to make sure to have less significant data as there may be crash problem in the system during testing.
  2. Test case generation- software testing test case generation is making different test cases which may cause error. Suppose a software which operates on fractions then setting the denominator of fractions as zero.
  3. Test case execution- After the execution of the test case, its result is analysed. It includes the checking of the inconsistency in the expected output for generated test case.
  4. Result and Analysis- When the test case is executed, its result is analysed. It includes the checking of the inconsistency in the expected output generated test case.
  5. Re-test– If the testing is failed then analysis of all the above steps is done to test the system.


  1. It helps us in the construction of an error-handling powered software.
  2. It makes the software ready for all circumstances.

Facebook Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

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

Related Articles

Back to top button