Software Testing-Manual Testing
Mainly in Manual Testing the following documents are required
i) Test Policy --QC
ii)Test Strategy--Company Level
iii) Test Factors--QA
iv)Test Methodology----TL
I)Test Policy: This is a company level document and will be developed by QC People.( At most management). This document defines
"Testing Objective" in that organization
- Small-scale company test policy
- Testing Def:
Verification + Validation
- Testing Process:
Proper planning before testing
- Testing Standard:
Defect per 280 LOC / Defect per 10 functional points
- Testing Measurements:
QAM (Quality Assessment Measurements),
TMM ( Test Management Measurements)
PCM (Process Capability Measurements)
II) Test Strategy: It is also a company level document and developed by QA people. It defines testing approach followed by testing team.
Components in Test Strategy:
-
Scope and Objective:
About testing need and their purpose
- Business Issues:
Budget control for testing in terms of time and cost
100%----Project Cost
64% Development & Maintenance and 36% for Testing
- Test Approach:
It defines mapping between development stages and testing issues
- Test Matrix (TM)/ Test Responsibilities Matrix (TRM)
- Test Deliverables:
Required documents to prepare during testing of a project
Ex: Test Methodology, Test Plan, Test case etc.,
- Roles & Responsibilies:
Names of jobs in testing team and their responsibility
- Communication and Status Reporting:
Require negotiations between two consecutive job in testing team
- Automation Testing Tools:
Need of automation in our organization level project testing
- Testing Measurements and Metrics:
QAM, TMM, & PCM
- Defect Reporting and Tracking:
Required negotiations between testing team and development team
- Risks & Mitigations:
Possible risks and mitigations to solve( risks indicates a future failure)
- Change and Configurations Management:
How to handle change requests coming from customers during testing and maintenance
- Training Plan :
Need of training to tester before starts of every project testing
III)Test Factors 1: To define quality S/W, quality analyst defines 15 testing issues. Test factor or issue means that a testing issue to apply on S/W to achieve quality.
The test factors are:
- Authorization:
Whether user is valid or not to correct application
- Access Control:
Authorized to access specific services
- Audit Trail:
Meta data about user operations
- Continuity of processing:
Inter process communication (IPC) during execution.
- Correctness:
Meet customer requirements in terms of inputs and out puts
- Coupling :
Co-existence with other existing S/W
- Ease of Use :
User friendliness of screens
- Ease of operate :
Installation, un installation, dumping, exporting etc.,
- File integrate:
creation of internal files (ex back up)
- Reliability:
Recover from abnormal situation
- Portable :
Run on different plat forms
- Performance :
speed of processing
- Service Levels :
order of services
- Methadology :
Follow standards
- Maintainable :
Long time serviceable to customers
2.Test Factors VS Black Box Testing Techniques
- Authorization :
Security Testing, Functional or requirement testing
- Access Control :
Security Testing ,if there is no separate team then Functional or Requirement testing
- Audit Trail :
Functionality or requirements, error handling testing
- Correctness :
Functionality or requirements testing
- Continuity of processing :
execution testing , operation testing (white Box)
- Coupling :
Intersystems testing
- Ease of use :
Usability testing
- Ease of operate :
Installation testing
- File Integrate :
Recovery , error handling testing
- Realiability :
Recovery ,Stress testing
- Portable:
Compatability,Configuration testing
- Performance:
Load & Stress ,Storage & Data volume testing
- Service Level :
Functionality or requirements testing
- Maintainable:
Compliance Testing
- Methodology:
Compliance Testing
IV)Test Methodology: It is a project level document and developed by QA(Quality Assurance Leader) or PMProject manager. It is a refinement form of Test Strategy. To prepare test methodology , QA or PM depends on below factors.
- Step1 :
Determine project type such as Traditional, Out sourcing and
Maintanence (depends on project type QA decreases no of columns in TRM)
- Step 2 :
Determine application requirements (depends on application requirements QA will decrease no of rows in TRM)
- Step 3:
Determine tactical risks (depends on risks, QA decrease no of factors in selected list)
- Step 4:
Determine scope of application (depends on expected future
enhancements, QA add some of the deleted factors to TRM)
- Step 5 :
Finalize TRM for current project
- Step 6 :
Prepare system test plan (defining scheduling for above finalized approach)---Test Lead will do
- Step 7 :
Prepare module test plans if require
More on Manual Testing
