Home »  Software Testing »  Manual Testing » Dynamic Testing

Dynamic Testing

Dynamic Testing

It is a testing phase conducted on the constructed/developed system, by providing the inputs and validating the outputs from the system. There are 2 major levels of dynamic testing performed:

White Box Testing Or Structural Testing

  1. Unit Testing
  2. Integration Testing

Unit Testing

It is also called as component testing in which the validation is done based on the knowledge of the internal structure of the system.

Integration Testing

Every unit or module tested and stable, all the  modules are united to form a system and the process of combing the modules is called as integration, checking the integration part is called as integration testing.

Stub : A simulation program that replaces the called program is  called Stub .

Driver : A simulation program that replaces the calling program is  called Driver .

Note : If there are any incomplete programs then instead of waiting till all programs are completed , programmer will develop stubs and drivers to carry out integration testing .

Black Box Testing Or Specification Based Testing

  1. System Testing
  2. Acceptance
  1. System Testing : A system is a final product, which is integrated, testing the whole application/product without the internal structural knowledge is called as system testing often test engineers are responsible in conducting it.
  2. Acceptance Testing: A testing phase conducted by the customer for whom the software is constructed, to accept the application is called as "user acceptance testing"

Testing Terminologies

Project : Is a software which is developed for a specific customer.

Product : A software which is developed for multiple potential end users.

Vendor : It is the Person Or A Firm, Who Is Involved In Developing The Software Or Providing
The Services In Both Project And Product.

Client :The Person Or A Firm For Whom The Software Is Constructed.

Customer :Is the actual person or a firm which uses the software constructed.

Note: the customers and client are the same in terms of a project but different for a product.

Template : It is a predefined structure with one or multiple fields. Templates are organizational level, which are developed based on the inputs from the standards. Common templates should be used for similar type of activities in all the projects.

Report : It is the summary of an activity performed. There can be different reports prepared at different levels, but there are two important reports prepared, they are:

A) Status Report:

Which specifies the progress of the project, they are two types:

  1. Weekly Status Report : A report with the progress during the test design phase
  2. Daily Status Report : A report with the progress during the test execution phase.

B) Defect Reports:

 A consolidated report prepared with the list of defects identified and reported along with their status.

Clarification Document (RCN)

It is a collection of all the queries or concerns for the team while analyzing or understanding the customer requirements.

Understanding Document

A document prepared by the team, with the level of understanding the requirements during the requirement analysis phase.

Knowledge Transfer(Kt)

It is session conducted to make the team understand what the requirements are this is carried out by the functional expert.

SME (Subject Matter Expert)

An expert in the domain or technology.


It the portion or a complete system/software/application/work product, which is constructed and ready for testing.


It the process of moving the constructed system(build) from the development environment to the test environment for further testing.


The document or the summary of an activity, which is provided to a team or a person is called as deliverable.

Ex: test deliverables:Test cases, test data, test scenarios, reports....

SRN ( Software Release Note )

It is a release note created by the developer and provided to the test team while deploying the build

DD ( Deployment Document )

A document which consists of the deployment process

Installation Document

An installation guide prepared and provided by the developer to the tester, while deploying the build

Unit Test Report

It is the summary of the test performed by the developer.

Test Set

It is a collection of several test cases to be executed on given build. It can be the collection of manual test cases or automation test script or combination of both.

Test Cycle

Executing all the test cases documented in a test set on a given build for one iteration is called as test cycle.

Issue Log

The problems or the challenges faced by the team during the process of validating the system. Every issue should be documented with the completed resolution process.

Test Execution

It is the process of validating the system or build (executing the test case). In this the status of the test would be -

Passed: If the expected is matching with the actual response from the system

Failed: If the expected is not matching the actual response.

Note : Every failed scenario is considered as a deviation and the deviation should be reported.

Traceability Matrix : It is mapping between the test cases and the customer requirements. It is to analyse the coverage of tc with respect to the requirements.

Contact Us| About Us| Terms| Privacy Policies
Powered by Lorquins Technologies© 2017 QuickToStudy.com. All Rights Reserved