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.
Software/Hardware used:
ASKED:
November 20, 2008 1:23 PM
UPDATED:
December 9, 2008 12:19 PM
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.