Task-Based Software Testing

Task-based program testing is the combination of a task analysis & an operational profile. The task analysis helps partition the input domain in to mission essential tasks & the technique functions which support them. Operational profiles, based on these tasks, are developed to further focus the testing effort.

Debugging Tests-
Debugging tests aims to find as many bugs as possible, either by sampling all situations likely to produce failures using methods such as code coverage and specification criteria, etc, or focusing on those considered most likely to produce failures, like stress tests, test methods and limits.
Study unit testing methods are examples of purification methods of proof. These include techniques such as statement testing, branch testing, basis path testing, etc. These methods typically are associated with some of the criteria based on coverage, which is sometimes referred to as methods of coverage. Debugging tests based on the assumption of an apparatus for measuring the types and locations of probable error.

Therefore, the effectiveness of this method depends largely on whether the assumptions of the examiner are correct.

If a developer and / or tester has a process in place to properly identify possible types and locations of the insects, then debug the tests can be very effective in finding errors. If a "standard" or "blind" approach is used, the statement into evidence for his own good, the effort of the tests may be ineffective and wasted. A subtle danger debugging testing is that you can discover many failures, but in the process of trial and effort wastes, regardless of the particular software upgrade, as the faults occur at a negligible rate in the work field.

Integration of test methods-
Historically, the developer of a system based on tests of debugging (which includes the functional or "proof-of-spec" test). Tests with the perspective of how the system employed was not observed until a testing operation (OTA), was involved. Even on those occasions when the test is developing a flavor of operation, this is seen as very late in the process. This historical approach amplifies the weak evidence of both operating and debugging of tests. I propose that the task-based software testing be accelerated to a point much earlier in the procurement process. This has the potential to counter the weaknesses of each method with the respective strengths.

Conclusions-
Task-based evaluation software is a combination test demonstrating the analysis of existing methods (task and operational testing). Its strength is in keeping with the strategy and operations of the mission and purpose of the essential tasks of the acquisition community to deliver operational capability quickly. By integrating software testing tasks with existing debug tests, the risk of meeting four customer concerns (over time, within budget, meets requirements and is reliable) can be reduced.