Validation?

• Dynamic, validating the actual product.
• Involves executing the product.
• Computer based execution of program.
• Target

1. Actual product
2. A Unit
3. A module
4. Set of integrated module
5. Final product

• Methods

1. Black Box
2. White Box
3. Grey Box   

Verification?

1. static, verifying, document, design ,code.
2. does not involving executing the code. 
3. Human based checking.
4. Target

1. Requirement specification
2. Application architecture
3. High level and detailed design
4. Data base design

• Methods

1. Inspection
2. Walk through
3. Desk-Checking

Quality Control Vs Quality Assurance ?

QA:- A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meets its objective.

• Process Related.
• focus on the processes used to developed a product.
• quality of the processes.
• Preventive control.
• Allegiance is to development.  

QC:- A set of activities designed to evaluate a developed product work.  

• Product related.
• testing of a product under development.
• Quality of the product.
• Detective control.
• allegiance is not to development. 

Software Development Life Cycle [SDLC]

How can be write Test Case ?

Purpose:-

Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions. 

Prerequisite:-

Assumptions that must be met before the test case can be run. E.g., "logged in", "guest login allowed", "user test user exists".

Test Data:-

List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combination of values. These values are written in set notation, one per line. E.g.:

loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}

password = {valid, invalid, empty}

Steps:-

Steps to carry out the test. See step formatting rules below.

1. visit LoginPage
2. enter userID
3. enter password
4. click login
5. see the terms of use page
6. click agree radio button at page bottom
7. click submit button
8. see PersonalPage
9. verify that welcome message is correct username

Expected Results:-  

A results which you will get after run/execute of a test case.

Actual Results:-

 After run a test case manual or automatically  the result should be match with actual result if it is match with the actual result your test case goes in to pass status otherwise fail.

Software Testing Life Cycle - STLC ?

Software testing life cycle identifies what test activities to carry out and when (what is the best time) to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.

Most comman Errors in software?

1. User Interface Errors:- Missing /Wrong function does not do what the user wants to expect.missing information, Inappropriate error message,performance issue ,Cant redirect o/p.
2. Error Handling:- Overflow,data comparison ,Error recovery,Aborting Error recovery from hardware Problems.
3. Boundary Related Errors:- Boundaries in loop,Space,Time,Memory,mishandling of case outside boundary.
4. Calculation Errors:-Bad logics,bad arithmetics outdated constant calculation error.wrong formulas,incorrect approximation.
5. Hardware.
6. Secure Version & id control.
7. Testing Errors.
8. Load Condition.
9. Control Flow Errors.