Professional Documents
Culture Documents
1)
2)
Static Testing
Dynamic Testing
Static Testing
Review
Informal Reviews
( Peer Review )
Technical Review
Lead Reviews
Management Review
Formal Review
( Inspections & Audits )
Walk Through
Techniques
Techniques
1)Statement Coverage
1)ECP ( EC / EP )
2)BVA
2)Path/Branch/Condition 3)Decision Table Testing
Coverage
4)State Transition Testing
5)Use Case Testing
* These Techniques are used to
Identify the Dead Code or Dead
Variables (That code or var not used
at any Point of time)
Static Testing:
Static Testing Is Considered As Verification Of The Documentation.
It Is Also Called As Verification Testing, Which Can Be Part Of All
The Stages In The Development Process And Which Starts At Very
Initial Stage.
There Are 2 Techniques Followed In The Static Testing Process, They
Are
1) Reviews:
2) Walkthroughs:
Reviews:
Reviews Are Part Of Static Testing Performed By The Quality
Assurance Team.
Benefits Of Reviews:
1. Defects Are Identified At Early Stage Of The Development Process
2. The Defects In The Later Stages Can Be Prevented.
3. Time And Efforts In Fixing The Defects Would Be Reduced
4. Will Improve The Quality Of The Product/Software/Application
Constructed.
5. Will Improve The Customer Satisfaction.
There Can Be Five Types Of Reviews Performed In A Project Process:
A) Peer Review (Informal Review):
A Review Phase On The Documentation Prepared, Conducted By The
Colleague With The Same Role Played In The Project.
B) Technical Review:
These Reviews will be conducted Among Technical Members to Decide
The Best Approach of Implementation when ever there is a Technical
Difficulty.
C) Lead Review:
1) Planning :
It is the First Phase of Formal Review Where the Author will send A
Formal Request to Moderator . Now the Moderator will Perform a
Entry Check to Confirm whether The Document is Eligible For
Review or Not , If Eligible Moderator Prepares A Review Plan and
Defines Exit Criteria.
a) Entry Criteria / Entry Check / Entry Condition
A Set of Pre Conditions to Start an activity is called
Entry Criteria
b) Exit Criteria / Exit Check / Exit Condition
A Set of Pre Conditions to Stop an activity is called Exit
Criteria
2) Kick Of Meeting :
This Meeting is helpful For Moderator to Explain The
Review Task and Also To Take The Time Commitment Form
Reviewers.
3) Preparation :
In This Phase All Reviewers will Start Reviewing The Job
Individually. During This Review Questions and Defects will be
Documented By Every Reviewer Individually.
4) Review Meeting :
All Participants Of Review Process That is Reviewers ,
Moderators including The Author Will Assemble & Discuss About The
Questions and Defects They Identified .The Accepted Defects Will be
Documented Separately By a Person Called Scribe / Recorder .
5) Re Work :
In This Phase Author will Rework on the Document to Fix
Defects.
6) Fallow Up : It is a Last Phase in Formal Review
Where the Moderator will Fallow Up all Reviews to
Ensure the Fulfillment Of Exit Criteria.
Audits:
It Is Also A Technique In Static Testing, But In Audit, The Process In
Implementing The Software Is Checked Rather Than The
Functionality Inside The Application Constructed.
As Part Of Audit The Audit Team Will Be Held Responsible To Check
The Following Things:
Checklist For Audit:
1. Are The Templates Used In All The Activities are Valid As Per The
Organizational Standards
2. Have The Naming Conventions Followed.
3. Are The Activities Carried As Per The Plan
4. Is Documentation Done For Every Single Activity Performed.
5. Are The Deliverables Prepared And Delivered In Time As Per The
Plan
Or
A) System Testing
B) Acceptance Testing
A) 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.
B) 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.
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: