Testing Relief will save your time and bring more quality into your software product.
...As you make changes in the program code, full testing becomes unnecessary. You only have to test those parts of the program code that were affected by the changes.
Current version is 1.0.1
Learn about all changes in your software product before you start testing it.
...Testing Relief does the expert's work - it analyzes all changes in a software product and detects parts of the program code that depend on these changes, but have not been modified themselves.
The Rational Unified Process (RUP) is an iterative software development
process framework created by the Rational Software Corporation, since 2002 a division of IBM.
The RUP is well known as the library of best practices of a project management.
Testing Relief is the tool for supporting "Test discipline" defined in RUP.
The purposes of "Test descipline" are:
to verify the interaction between objects;
to verify the proper integration of all components of the software;
to verify that all requirements have been correctly implemented;
to identify and ensure that defects are addressed prior to the deployment of the software.
Testing applications
The task of testing applications comes down to checking how changes in the source code of the software product influence its entire functionality and quality.
Testing can be divided into two types: full and partial.
Full software product testing
Full testing implies testing all functions and visual elements in a software product.
The advantage of full testing is detecting all bugs and defects in the software product.
The disadvantage of full testing is that it requires a considerable amount of time.
To reduce the time necessary to test large software products manually, developers use automatic tools for testing applications - unit tests- that are supported by the methodology of software product development called TDD (Test Driven Development). The main drawback of TDD is that unit tests are program code that has to be modified as well in case the source code of the software product is considerably modified. Another question left unsolved is testing unit tests themselves.
Partial software product testing
Partial software product testing means testing only those parts of the program code that have been affected by changes. At the same time, you should take into account both those parts of the software product that were actually modified and those parts of it that the modified parts indirectly affected. Only an expert that possesses the necessary knowledge about the software structure can detect such dependencies.
Partial testing allows you to considerably reduce the amount of work related to testing, including both testing and the preparation required for it, for instance, when unit tests are used.
Testing optimization
The optimal process of testing a software product looks like this. First, you test the entire software product, all its functions and visual elements. As you make changes in the program code, full testing becomes unnecessary. You only have to test those parts of the program code that were affected by the changes.
This approach saves a lot of time, which allows you to increase the quality of testing.
The role of Testing Relief
Testing Relief does the expert's work - it analyzes all changes in a software product and detects parts of the program code that depend on these changes, but have not been modified themselves.
Thus, Testing Relief shows the whole picture of changes in the software product and determines the amount of work necessary to perform testing
). The main drawback of TDD is that unit tests are program code that has to be modified as well in case the source code of the software product is considerably modified. Another question left unsolved is testing unit tests themselves.