Test Strategy

Smoke testing confirms the basic functionality works for a product. It requires you to identify the most basic test cases for execution.

Sanity testing, on the other hand, ensures that the product runs without any logical errors. For example, if we are testing a calculator app; we may multiply a number by 3 and check whether the sum of the digits of the answer is divisible by 3.

Gap analysis reveals any deviation between the features available for testing and how the customer perceives them to be. Traceability matrix is a testing tool which testers can use to track down the gaps.

Static Testing - It is a white box testing technique which directs the developers to verify their code with the help of checklist to find errors in it. Developers can start it done without actually finalizing the application or program. Static testing is more cost effective than dynamic testing. It covers more areas than dynamic testing in a shorter time.

Dynamic Testing - Dynamic testing involves the execution of an actual application with valid inputs and checking of the expected output. Examples of dynamic testing are Unit Testing, Integration Testing, System Testing and Acceptance Testing. Dynamic testing happens after the code deployment. It starts during the validation stage.

It is none other than the Functional specification document. It defines the full functionality of a product. Other documents are also useful in testing like user manual and BRS. Gap analysis is another document which can help in understanding the expected and existing system.

BRD provides a detailed business solution for a project including the documentation of customer needs and expectations.

Risk analysis is a technique to identify the things that can go wrong in a software development project. They can negatively impact the scope, quality, timeliness, and cost of a project.

Exploratory testing is a process which lets a tester to concentrate more on execution and less on planning. It requires formulating a test charter, a short declaration of the scope, set of objectives and possible approaches to be used.

No. The system testing should start only if all modules are in place and work correctly. However, it should happen before the UAT (User Acceptance testing).

Traceability matrix is an intuitive tool which ensures the requirements mapped to the test cases. And when the execution of all test cases finishes with success, it indicates that the code has met the requirements.

It is a test case design technique in which testers have to guess the defects that might occur and write test cases to represent them.

It is the process of adding known bugs in a program for the tracking the rate of detection & removal. It also helps to estimate the number of faults remaining in the program.

Cohesion is the degree which measures the dependency of the software component that combines related functionality into a single unit whereas coupling represents the binding of related functionality into a different unit.

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for assessing the maturity of the software processes of an organization and for identifying the key practices that increase the maturity of these processes.

It is a graphical representation of inputs and the associated outputs effects which assist in designing test cases.

The test strategy includes an introduction, resource, scope and schedule for test activities, test tools, test priorities, test planning and the types of test that has to be performed.

The testing of all the branches of the code, which is tested once, is known as branch testing.  While the testing, which is focused on the limit conditions of the software is known as boundary testing.