When attempting to build an application that needs to interface with an application on a mainframe computer, but no mainframe is available during development, a test harness may be built to use as a substitute this can mean that normally complex operations can be handled with a small amount of resources by providing pre-defined data and responses so the calculations performed by the mainframe are not needed.
A test harness may be part of a project deliverable. It may be kept separate from the application source code and may be reused on multiple projects. A test harness simulates application functionality; it has no knowledge of test suites, test cases or test reports. Those things are provided by a testing framework and associated automated testing tools.
A part of its job is to set up suitable test fixtures.
The test harness will generally be specific to a development environment such as Java. However, interoperability test harnesses have been developed for use in more complex systems.4
"Test Harness". ISTQB Glossary. Retrieved 10 September 2023. https://glossary.istqb.org/en_US/term/test-harness-3-2 ↩
Rocha, Camila Ribeiro; Martins, Eliane (2008). "A Method for Model Based Test Harness Generation for Component Testing". Journal of the Brazilian Computer Society. 14: 8. doi:10.1007/BF03192549. Retrieved 10 September 2023. https://rdcu.be/dlLqi ↩
ISTQB Exam Certification - "What is Test harness/ Unit test framework tools in software testing?", accessed 19 October 2015 http://istqbexamcertification.com/what-is-test-harness-unit-test-framework-tools-in-software-testing/ ↩
Ricardo Jardim-Gonçalves, Jörg Müller, Kai Mertins, Martin Zelm, editors, Enterprise Interoperability II: New Challenges and Approaches, Springer, 2007, p. 674, accessed 19 October 2015 https://books.google.com/books?id=JZRDvNC78ZcC&q=%5B3%5D&pg=PA650 ↩