Professional Documents
Culture Documents
1. You are a tester for testing a large system. The system data model is very
large with many attributes and there are a lot of interdependencies within
the fields. What steps would you use to test the system and also what are
the effects of the steps you have taken on the test plan? OR
You are the test manager for about to the system testing. The development
team says that due to change in requirements, they will be able to deliver
the system to you for testing 5 working days after the due date. You cannot
change the resources (Work hours, days, test tools). What steps will you
take to be able to finish the testing in time?
Solution
Improve Supervision: More reviews of artifacts or program means Stage
containment of the defects.
Creation of Base Line Data which is accurate and updated.
Strict Change Management: Correct versions are tested.
Phase wise / module wise approach for the testing.
More focus on Module and Integration testing.
Add more resources.
Work With Independent Test Team.
Automation for regression testing.
Rank the functionality as per risk and concentrate more on critical functionality
testing
Effective Communication - Reporting of critical defects (Using defect
tracking/management system) and resolution plan discussion with development
team
Traceability matrix of changed requirement and Impact Analysis documents
creation
Test cases updating as per Changed requirement
Exit criterion is achieved , release product
Solution:
Test Plan:
Scope
Objective
Assumptions
Risks
Roles and Responsibilities
Test Environment
Tools
Schedule
Test Design
Test data Management
Communication
Test Script:
Sequence
Source : Data Entry Operator
Script Event : Enter Invalid Input
Evaluation Criterion : Error Message Should be Displayed
Comments : Help regarding valid Input
CSTE Test Cases
Solution
- Project description
- Scope
- User roles and responsibilities
- Acceptance criteria
- Test cases to be executed
Acceptance Criterion
-----------------------------------------------------------------------------------------------
No Acceptance req Critical Result Remark
Yes No Accept Reject
-----------------------------------------------------------------------------------------------
1 Login time - should not be Yes Yes Accept
more than 6 sec
Solution
To find defects
To ensure that it meets user requirements
To ensure that it is fit for use
To reduce cost of quality by delivering defect free product
To achieve customer satisfaction
Continuously improving test process
Reduce risk of software failure
To determine the state of software.