What is the task of testing applications?

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. Besides, unit tests have a limited scope of use, in particular they are used only to test code libraries. Taking into account expenses on creating unit tests themselves, the efficiency of their use increases together with the increase in the stability of the software product, which, in its turn, reduces the motivation for their use. 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 have 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.
Another means of reducing the time necessary to test the quality of a software product is statistical software code analyzers.

The reasons for their use come down to reducing the amount of code that requires to be analyzed by a human. Here it is also possible to use tools for target diagnostics of certain properties in the program under development. You can take the statistical analyzer Viva64 (http://www.Viva64.com) as an example. It is used to verify the code of a program when it is ported to the 64-bit platform.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Dharmendra Gaur17y ago
Accepted answer
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. Besides, unit tests have a limited scope of use, in particular they are used only to test code libraries. Taking into account expenses on creating unit tests themselves, the efficiency of their use increases together with the increase in the stability of the software product, which, in its turn, reduces the motivation for their use. 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 have 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.
Another means of reducing the time necessary to test the quality of a software product is statistical software code analyzers.

The reasons for their use come down to reducing the amount of code that requires to be analyzed by a human. Here it is also possible to use tools for target diagnostics of certain properties in the program under development. You can take the statistical analyzer Viva64 (http://www.Viva64.com) as an example. It is used to verify the code of a program when it is ported to the 64-bit platform.
Ankur Agarwal17y ago
Thanx for your reply nikhil.

But this is not the answer for what i asked to.

I asked about the task of testing applications not the software testing types or methods.