Software Testing Strategy Approach On Source Code Applying Conditional Coverage Essay

Fault Tolerant testing is used to verify that the packages actions does not perform in detrimental nor unexpected ways for input parameters that could be illegal or out of range, and have the required catches in place to help prevent these input parameters being used; fault tolerant testing ensures that the software works smoothly and as elegantly as possible.

Test (or) Code coverage is a measure used to describe the degree to which the source code of a program is tested by a particular test case/suite. In other words, Code coverage is a way of ensuring that your tests are actually testing your code. Coverage acts as an effective approach to determine the efficiency of your test case (or a set of test cases); knowledge of the internals of the object being tested shall be known to (white/black-box) test and helps in test case optimization.

Any IT solution that is implemented without proper method of testing in project is a sure anticipation of failure. Testing is an ongoing process both formally and informally. Testing happens in different stages of software development life cycle like in development, actual testing phase and in post-deployment phase.

The objective of software testing technique is to expose failures. Testers prioritize inputs based on the acquired quality attribute, e.g., correctness, robustness, reliability, security. When high reliability is to be achieved, tester wishes to sample those failure-causing inputs that have the largest impact on failure probability. This is the procedure followed by techniques based on the expected operational profile to derive tests. Testing software pose many practical challenges for assessing or improving reliability. General Operational testing is a fundamental strategy that simulates the real usage of the system in order to expose failures with the highest occurrence probability. Testing relied on operational profile estimation, known as operational testing, is considered as the natural approach to test software for reliability assessment or improvement.

Software testing is any activity aimed at evaluating an attribute or capability of a program or system and determining that it meets its required results. [Hetzel88] Although crucial to software quality and widely deployed by programmers and testers, software testing still remains an art, due to limited understanding of the principles of software. The difficulty in software testing stems from the complexity of software: we can not completely test a program with moderate complexity. Testing is more than just debugging. The purpose of testing can be quality assurance, verification and

There are many metrics and tools used in the software industry that attempt to describe the effectiveness, usefulness and completeness of software tests. A common metric of “test coverage”, also known as “code coverage”, is used to quantify how much code of a particular program that tests are covering. Test coverage however does not require that the tests are of high quality, and does not require the tests to take into account how a program may change or evolve over time. Because of this, a program with a quantitatively high test coverage is not necessarily a program that has effective tests that will spot changes, or “mutations”, in the code. Code is constantly being modified, added, and removed during a normal software development process. It is important for programs to have tests that are effective throughout the development process.

Integration tests are used to test integrated software components that determines they actually run as one program. This testing is more concerned and the event driven with the basic outcome of the fields or screens. Integration tests demonstrate that even the components were individually satisfaction, as shown before by the successful unit testing, the both combination of the component is consistent and correct. Integration testing is mainly used at showing the problem that arise from the combination of components.

In general, the testers encounter the problem of removing the logical errors and bugs. The test conditions which are decided in the analysis phase are applied to the system and if the output obtained is equal to the intended output, it means that the software is ready to be provided to the user.

Black box testing is a technique of testing without having any knowledge of the interior workings of the application. The tester is insensible to the system architecture and does not have any access to the source code. Usually, while performing a black-box test, a tester will interact with the system's UI by providing inputs and examining outputs without knowing how and where the inputs are worked upon. There are some advantages and disadvantages of black-box testing which are as follows.

In this strategy some test cases are generated as input conditions that fully execute all functional requirements for the program. This testing has been uses to find errors in the following categories:

When a web application is developed with some specific goal in mind, those peculiarities which segregate them from any other software application also affects their testing in several ways. These changes may result in harder than traditional testing and to accomplish them successfully we need to employ different testing methodologies. Following are some of the most common testing methodologies available in the testing domain

In both stages of system testing, black box testing techniques are used to test the functions of the system to verify and validate the business requirements have been met.

Daz et al. [47] derived a Tabu Search Generator (TSGen) for automatic structural software testing with intensified and diversified search to attain high branch coverage. It also uses memory mechanisms and backtracking to escape

Software engineering provides the framework for building the high quality software. It integrates the various strategies, methods and tools for the software development. The revolution of software engineering offers the different types of software development models. It majorly ratifies the performance of the software through the testing and maintenance phase of the software.

In this part of testing, basically unit testing is done on each part of project to test the different outcomes from different inputs. In this testing the main point is that the tester tries to end-up with a desired solution for the given situation.