Unit Testing Framework

Context:
- It can (typically) be used to create a Unit Testing System.
- It can support Test Automation, sharing of setup and shutdown code for tests, aggregation of tests into collections, and independence of the tests from the reporting framework.
- …
Example(s):
- Python Code Unit Testing Framework, such as: unittest, pytest).
- Java Code Unit Testing Framework, such as: JUnit.
- Scala Code Unit Testing Framework.
- NUnit.
- …
Counter-Example(s):
- a Test Case Management Tool, such as test.
- an Integration Testing Framework.
- …
See: Source Code, Software Testing, Mocking Framework.

References

(Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/List_of_unit_testing_frameworks Retrieved:2021-3-11.
- This page is a list of tables of code-driven unit testing frameworks for various programming languages. Some, but not all, of these are based on xUnit.

https://docs.python.org/3/library/unittest.html
- QUOTE: ... It supports test automation, sharing of setup and shutdown code for tests, aggregation of tests into collections, and independence of the tests from the reporting framework.

(Wikipedia, 2018) ⇒ https://en.wikipedia.org/wiki/Unit_testing#Unit_testing_frameworks Retrieved:2018-12-12.
- Unit testing frameworks are most often third-party products that are not distributed as part of the compiler suite. They help simplify the process of unit testing, having been developed for a wide variety of languages. Examples of testing frameworks include open source solutions such as the various code-driven testing frameworks known collectively as xUnit, and proprietary/commercial solutions such as Cantata for C/C++Typemock Isolator.NET/Isolator++, TBrun, JustMock, Parasoft Development Testing (Jtest, Parasoft C/C++test, dotTEST), Testwell CTA++ and VectorCAST/C++.
  It is generally possible to perform unit testing without the support of a specific framework by writing client code that exercises the units under test and uses assertions, exception handling, or other control flow mechanisms to signal failure. Unit testing without a framework is valuable in that there is a barrier to entry for the adoption of unit testing; having scant unit tests is hardly better than having none at all, whereas once a framework is in place, adding unit tests becomes relatively easy. In some frameworks many advanced unit test features are missing or must be hand-coded.