Static and Dynamic Testing

Topics

:- QA Vs QC

:- Verification V/s Validation

:- Static V/s Dynamic Testing

:- Review, Walkthrough & Inspection





QA V/s QC

:-QA is process related                       QC is the actual testing of the software

:-QA focuses on building in quality                        QC focuses on testing for quality

:-QA is preventing defects                        QC is detecting defects

:-QA is process Oriented                        QC is product Oriented.

:-QA is for entire life Cycle                        QC is for testing part in SDLC

:-QA focuses on building quality                       QC focuses on testing for quality and hence detecting defects

and hence preventing defects

:-Quality Assurance makes sure                        Quality control makes sure the results of what you done you are doing the right things, are what you expected.

the right way. fit for purpose & right first time                     to achieve Reliability, maintainability & safety



Verification V/s Validation

Verification checks whether we are building the right system

Verification is a process of finding out the product being developed the right way?

Verification typically involves

:-Review

:-Walkthroughs

:-Inspections

:- Buddy Check

Validation checks whether we are building the System Right

Validation is a process of finding out if the product being developed is right?

-- Generally Takes place after verification are completed

-- Validation typically involves actual Testing Like System Testing.

Reviews :-

Conducts on documents to ensure correctness and completeness.

Examples :-

:- :- Requirement Reviews

:- :- Design Reviews

:- :- Code Reviews

:- :- Test Plan Reviews

:- :- Test Cases Reviews etc.

Phases of Review :-

:- :- Planning

:- :- Kick-off

:- :- Preparartion

:- :- Review Meeting

:- :- Rework

:- :- follow up

Walkthroughs :-

:- :- It is a formal review and we can discuss/raise the issue at peer level.

:- :- Also walthrough does not have minutes of the meeting/meet. It can happen at any time and conduct just like that no schedule as such.

Inspections :-

:- :- It is a formal approach to the requirements schedule.

:- :- At lest 3-6 people will sit in the meeting 1-reader 2- writer 3- moderator plus concerned.

:- :- Inspection will have a proper schedule which will be intimated via email to the concerned developer/Tester.

Buddy Check :-

One person goes through the documents prepared by another person in order to find out if that person has made mistakes i.e. to find out bugs which the author couldn't find previously.

Static V/s Dynamic Testing



:- Static testing is an approach to test project documents in the form of

:- :- Reviews

:- :- Walkthroughs

:- :- Inspections

Dynamic Testing is an approach to the actual Software by giving inputs & performing operation and observing results.