Scribd
Upload
7 views14 pages

Test Phases

The document outlines the syllabus for the Software Testing and Automation course at KGiSL Institute of Technology, detailing the test planning process, phases, strategy, resource requirements, and tester assignments. It emphasizes the importance of defining entrance and exit criteria for each test phase and the need for a well-structured test strategy. The course aims to equip students with the skills to plan and execute test cases effectively.

Uploaded by

Mohammed irfan m Mansoor ali t a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
7 views14 pages

Test Phases

The document outlines the syllabus for the Software Testing and Automation course at KGiSL Institute of Technology, detailing the test planning process, phases, strategy, resource requirements, and tester assignments. It emphasizes the importance of defining entrance and exit criteria for each test phase and the need for a well-structured test strategy. The course aims to equip students with the skills to plan and execute test cases effectively.

Uploaded by

Mohammed irfan m Mansoor ali t a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

KGiSL Institute of Technology

(Approved by AICTE, New Delhi; Affiliated to Anna University, Chennai)


Recognized by UGC, Accredited by NBA (IT)
365, KGiSL Campus, Thudiyalur Road, Saravanampatti, Coimbatore – 641035.

Department of Computer Science and Engineering

Name of the Faculty : Ms. A. Suganthi

Subject Name & Code : CCS366/ Software Testing and Automation

Branch & Department : Computer Science and Engineering

Year & Semester : III / VI

Academic Year :2024-25


Syllabus

UNIT II TEST PLANNING


The Goal of Test Planning, High Level Expectations, Intergroup
Responsibilities, Test Phases, Test Strategy, Resource
Requirements, Tester Assignments, Test Schedule, Test Cases,
Bug Reporting, Metrics and Statistics.
COURSE OUTCOME

CO2: Determine the activities involved in planning and executing


test cases
TOPIC

TEST PHASES

CCS366/STA/III CSE/VI SEM/KG-KiTE


Test Phases
• To plan the test phases, the test team will look at the proposed
development model and decide whether unique phases, or stages, of
testing should be performed over the course of the project.
• In a code-and-fix model, there’s probably only one test phase—test
until someone yells stop. In the waterfall and spiral models, there can
be several test phases from examining the product spec to
acceptance testing. Yes, test planning is one of the test phases.
• The test planning process should identify each proposed test phase
and make each phase known to the project team. This process often
helps the entire team form and understand the overall development
model.
Test Phases
• Two very important concepts associated with the test phases are the
entrance and exit criteria.
• Each phase must have criteria defined for it that objectively and absolutely
declares if the phase is over and the next one has begun.
• For example,
• the spec review stage might be over when the minutes to the formal spec review
have been published.
• The beta test stage might begin when the testers have completed an acceptance
test pass with no new bugs found on the proposed beta release build.
• Without explicit entrance and exit criteria, the test effort will dissolve into
single, undirected test effort—much like the code-and-fix development
model.
CCS366/STA/III CSE/VI SEM/KG-KiTE
Test Phases
1. Requirement Analysis
2. Test Planning
3. Test Case Design & Development
4. Test Environment Setup
5. Test Execution
6. Defect Reporting & Tracking
7. Test Closure & Reporting

CCS366/STA/III CSE/VI SEM/KG-KiTE


Test Strategy
• An exercise associated with defining the test phases is defining the
test strategy.
• The test strategy describes the approach that the test team will use to
test the software both overall and in each phase
• Example:
• If you were presented with a product to test, you’d need to decide if it’s
better to use black-box testing or white-box testing.
• If you decide to use a mix of both techniques, when will you apply each and
to which parts of the software?

CCS366/STA/III CSE/VI SEM/KG-KiTE


Test Strategy
• It might be a good idea to test some of the code manually and other code
with tools and automation.
• If tools will be used, do they need to be developed or can existing
commercial solutions be purchased? If so, which ones? Maybe it would be
more efficient to outsource the entire test effort to a specialized testing
company and require only a skeleton testing crew to oversee their work.
• Deciding on the strategy is a complex task—one that needs to be made by
very experienced testers because it can determine the success or failure of
the test effort.
• It’s vitally important for everyone on the project team to understand and
be in agreement with the proposed plan.

CCS366/STA/III CSE/VI SEM/KG-KiTE


Resource Requirements
• Planning the resource requirements is the process of deciding what’s
necessary to accomplish the testing strategy. Everything that could
possibly be used for testing over the course of the project needs to be
considered.
• For example:
• People. How many, what experience, what expertise? Should they be
full-time, part-time, contract, students?
• Equipment. Computers, test hardware, printers, tools.
• Office and lab space. Where will they be located? How big will they
be? How will they be arranged?
• Software. Word processors, databases, custom tools. What will be
purchased, what needs to be written?
CCS366/STA/III CSE/VI SEM/KG-KiTE
Resource Requirements
• Outsource companies. Will they be used? What criteria will be used
for choosing them? How much will they cost?
• Miscellaneous supplies. Disks, phones, reference books, training
material. What else might be necessary over the course of the
project?

• The specific resource requirements are very project-, team-, and


company-dependent, so the test plan effort will need to carefully
evaluate what will be needed to test the software.
• It’s often difficult or even impossible to obtain resources late in the
project that weren’t budgeted for at the beginning, so it’s imperative
to be thorough when creating the list.
CCS366/STA/III CSE/VI SEM/KG-KiTE
Tester Assignments
• Once the test phases, test strategy, and resource requirements are
defined, that information can be used with the product spec to break
out the individual tester assignments.
• The inter-group responsibilities discussed earlier dealt with what
functional group (management, test, programmers, and so on) is
responsible for what high-level tasks.
• Planning the tester assignments identifies the testers responsible for
each area of the software and for each testable feature. Table shows
the example of a tester assignments table for Windows WordPad

CCS366/STA/III CSE/VI SEM/KG-KiTE


Tester Assignments
• A real-world responsibilities table would go into much more detail to
assure that every part of the software has someone assigned to test
it. Each tester would know exactly what they were responsible for and
have enough information to go off and start designing test cases.

CCS366/STA/III CSE/VI SEM/KG-KiTE


THANK YOU!!!

You might also like