Interested to Buy Any Domain ? << Click Here >> for more details...
what is test harness?
- 4 Answers
- 7413 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / amol manjrekar
Test Harness is a program or a test tool used to execute a
test.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / rudraneel
Test Harness is an environment of Stubs & Drivers needed to
execute a test
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / nams
“A test harness simply is to create the correct framework and use it (and all of its constituent elements) to control the entire activity as to get the most of the situation- whether automation or integration.
it is time to explore what Test harness means in the context of “Integration Testing”.
Integration testing is to put together two or modules (or units) of code that interact with each other and to check whether or not the combined behavior is as expected or not.
Ideally, Integration testing of two modules should and would be possible to carry out when both of them are 100% ready, unit tested and good to go.
However, we do not live in a perfect world- which means, one or more modules/units of code that are to be the constituent elements of the integration test might not be available. To solve this situation we have stubs and drivers.
Stud is usually a piece of code that is limited in its function and will substitute or proxy for the actual module of code that needs to take its place.
Example: To further explain this, let me use a scenario
If there is a unit A and Unit B that are to be integrated. Also, that Unit A sends data to Unit B or in other words, Unit A calls Unit B.
------------
Unit A if 100% available and unit B is not, then the developer can write a piece of code that is limited in its capability ( what this means is the Unit B if it has 10 features, only 2 or 3 that are important for integration with A) will be developed and is used for integration. This is called a STUB.
The integration would now be: Unit A->Stub (substituting for B)
On the other hand, if Unit A is 0% available and Unit B is 100% available, the simulation or proxy has to be Unit A here. Therefore when a calling function is replaced by auxiliary code, then it is called the DRIVER.
The integration in this case would be: DRIVER (substituting for A) -> Unit B
The entire framework: The process of planning, creating and usage of stubs and/or drivers to carry out the integration testing is called the Test Harness.
| Is This Answer Correct ? | 0 Yes | 0 No |
SAY YOUR PRODUCT PASSED THROUGH TESTING & UAT. NOW IT WENT TO PRODUCTION AT CLIENT LOCATION AND THEY FOUND ONE DEFECT IN IT. HOW THEY NEED TO PROCEED NOW? WILL THEY CONTACT U? OR WILL THEY CONTACT DEVELOPMENT TEAM?
After insert the record in front-end, how will you check the back end by manually? Please explain?
what is difference between testing and development in your view?
what is positive and negative testing explian with example?
11 Answers Accenture, Qutesys, Sabic,
does tester use design document for writing testcases
what is prototyping model,RAD model V model, spiral model?????
What techinques do you follow during testing?
Write 5 Test Cases for ATM From Security Point of View ?
How load testing is different from regression testing?
What is the difference between windows application and Client server application ?
I need some help. Could you solve this query i got this query the other day. Any help would be appreciated Write down any potential problems or omissions from this Fault Log Fault no: 278 Environment: Windows 98 Priority:3 Tester:Author Application: Web testing Description When i log onto the screen DF342 I should be able to delete records. However when trying to delete records an error message appears telling mw that im not authorized Response: 25 Aug: Programmer: Security needs to be setup providing access to the delete facility- No error 26 Aug:Tester: We had Security up and it doesnt seem to work- I have reopened this fault
what is cross project reference what is entry and exit criteria for login page.
Automation Testing 
