V&V-Model -Testing Levels in V model

1. Testing is Started from system requirement phase

2. During the initial testing verification conducted, on the application validation is done

3. Testing = Verification - validation

Verification

It can be conducted on the documents application to ensure are we developing the right product are not just verification

Validation

It is conducted on the application to ensure the develop product is working as per requirement are not 
Static testing: Testing the Application without executing (Verification)

Dynamic Testing: Executing the application give input data and validate the application as per the requirement (Validation)

TESTING LEVELS IN V-MODEL

1. REQUIREMENT REVIEW: - After requirements are prepared reviews are conducted

 For completeness and correctness

2. DESIGN REVIEWS:-HLD AND LLD

After the design is prepared reviews are conducted to ensure the completeness and correctness of the design

1. Verify the design login is good

2. Verify the design is possible to understand the developers

3. UNIT TESTING

1. Developers can due the testing is called unit testing

2. Testing is conducted by developers or white box testers

3. Testing is conducted on single program or single component

4. To conduct unit testing programming knowledge is called developers

Unit testing is a test (often automated) that validates that individual unit of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method, which may belong to a base/super class, abstract class or derived/child class.

Ideally, each test case is independent from the others; Double objects like stubs, mock or fake objects as well as test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by software developers to ensure that the code they have written meets software requirements and behaves as the developer intended.

What should be tested when Unit Testing: A lot depends on the type of program or unit that is being created. It could be a screen or a component or a web service. Broadly the following aspects should be considered:

a. For a UI screen include test cases to verify all the screen elements that need to appear on the screens
b. For a UI screen include Test cases to verify the spelling/font/size of all the “labels” or text that appears on the screen
c. Create Test Cases such that every line of code in the unit is tested at least once in a test cycle
d. Create Test Cases such that every condition in case of “conditional statements” is tested once
e. Create Test Cases to test the minimum/maximum range of data that can be entered. For example what is the maximum “amount” that can be entered or the max length of string that can be entered or passed in as a parameter
f. Create Test Cases to verify how various errors are handled
g. Create Test Cases to verify if all the validations are being performed

In tester what is risk

Check the syntax in pro grammatically

Basis for testing, test each line and each time

If conditional statements and loops and branches etc---

4. INTEGRATION TESTING

 Testing is conducted by combination two or more components with in the same system or two systems are integrated.

Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested

It is a testing in which units will be tested; these units will be combined or integrated to form complete system

Between the modules (or) between the features.

5. SYSTEM TESTING

1. It is responsibility of testers to conduct system testing

2. Testing is conducted based on the customer requirement

3. Testing ids conducted after the complete development is done

4. During system testing FUNCTIONAL TESTING AND NON FUNCTIONAL TESTING

These procedures tell the tester how the system should perform and where common mistakes may be found. Testers usually try to "break the system" by entering data that may cause the system to malfunction or return incorrect information. For example, a tester may put in a city in a search engine designed to only accept states, to see how the system will respond to the incorrect input.

1.       Functional testing

2.       Non-functional testing

6. UAT:

1. Beta testing