Professional Documents
Culture Documents
Ans: For Developers we use 'Interim Test Results' and for management we give 'Summary Report' and
project Status Report' .
Hi All,
a) Lifestyle
b) Vocabulary
c) Internal
d) Management
a) $2630
b) $8770
c) $1600
d) $8600
3. The ______________ is an application of process management
and quality improvement concepts to software development and
maintenance.
a) Malcolm Baldridge
b) ISO 9000
c) SEI/CMM
d) QS14000
* True * False
* True * False
Ans: Testing the interfaces between the unit tested programs as well as between
components.
Ans: True.
Ans: True.
Ans: TopDown
Ans: HardWare.
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
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
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.
2. 1. What are the different names of Exploratory Testing?
2. Where does Exploratory Testing come in to existence in testing
lifecycle [whether it comes under Unit testing, Integration
testing
System testing, etc]?
3. Where does this exploratory testing comes in V-Model?
4. Whether Exploratory testing comes under Black box or White box
testing?
5. How to measure Exploratory Testing?\
3. You are given two scenarios to test. Scenario 1 has only one
terminal for entry and processing whereas scenario 2 has several
terminals where the data input can be made. Assuming that the
processing work is the same, what would be the specific tests in
Scenario 2 that you would do, which you would not carry on
Scenario
1? (V. IMP question)
- Integrates systems engineering and software engineering disciplines into one process
improvement framework
TEST POLICY
CSTE GROUP LTD
Testing Definition:
Determination of the validity of the computer solution to a business
problem .
Testing System:
Development and execution of a test plan in accordance with
departmental procedures and user requirements.
Measurement of Testing
Cost of undetected defects.
Testing Standards
One defects per 250 executable program statements.
• Planning - Documenting test requirements and strategies, defining procedures, providing testers
with step-by-step instructions
• Executing - Carrying out test procedures, including proofreading for grammar, spelling, consistent
word usage and text layout, monitoring performance, validating links, ensuring usability across
various platforms and browsers
• Evaluating - Reporting test results and suggested actions for unexpected test results to
development staff and to client’s best wishes