Frequently i am hearing that we need to do perform Break testing before product goes to customers UAT.
I want to understand break testing and use it efficiently.
What exactly break testing means?
I heard it is forced-error testing where we build dummy stubs simulating our servers product server, DB server, etc) which will take requests but not send responses, sending invalid responses. what else the dummy stubs can do?
Whey we have to perform break testing?
What kind of issues we can get which we will not get in functional, load testing?
And How to do this Break testing? like How to simulate dummy DB servers, dummy data base drivers etc?
Thanks in advance.

Answer Wiki

Break Testing is more than just “force fail.” It is creating tests that will fail for various reasons such as latency, invalid responses, incomplete/unacceptable data… the list of what break testing should test is long.

The surest way to find out what needs to be “break tested” is by first looking at the code and finding out what is “invalid”. Second, look at the requirements documentation and see what is “unacceptable.” If you test for proper handling of both invalid and unacceptable conditions, you will find your code much better accepted in UAT.

As an aside (but an important one) be sure you have documented the type of responses that will occur in invalid and unacceptable circumstances. Make sure that documentation is in layman’s terms (simple, non-technical) and make sure the user community understands and approves of how the exceptions are handled.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your response...

Discuss This Question: 2 &nbspReplies

There was an error processing your information. Please try again later.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

The break testing is equally important to find out the response of system in case of hardware/software failures. The type of the break testing includes lost connetion to database, network, invalid requests... anything that is unpredictable and breaks the normal path of execution for the system.
The reason for performing the break testing is to confirm to the expected system behaviour in case of any breakage. This is to validate the treatment for atomic transaction and handling of intermediate state of data. The restart and recovery part of the overall architecture plays very important role in defining the conditions for break testing.
The break testing needs to be fecilitated by the infrastructure support groups and development team. They are needed to create the scenario and analyze the results.

Thanks for your comment.
Can u give some pointers on the below point u mentioned:
The restart and recovery part of the overall architecture plays very important role in defining the conditions for break testing.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy

Processing your reply...

Ask a Question

Free Guide: Managing storage for virtual environments

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!

To follow this tag...

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy