STQA

Testing Strategy :-
Testing strategy is a high-level plan which guides the testing process, reducing
risks, ensuring efficiency of a software. Minimize the risks by :
Early Testing : Start testing when development begins to catch bugs early.
Risk-Based Testing : Focus on testing the most critical features first.
Automation : Use Test Automation for repetitive tasks to save time & reduce
errors.
Test in Different environments : Ensure testing in real world conditions
(different devices, different network speeds, diff. browsers).
Security & performance testing : Chk for vulnerabilities & ensure smooth
performance before release.

The Testing Environment is the setup where the software is tested. It includes
Hardware, software, sample data, tools & frameworks.
Think of it like a lab setup where scientists test medicines before launching
them!
Testing Policy :-
It’s the document that defines the rules & standards for testing for testing in
organization. A good testing policy ensures consistency, accountability, and
quality in the testing process. Key elements :-
Goals & Objectives : What do we wanna achieve? (bug-free soft. , security
compliance) .
Types of testing used : Manual, automation, performance, security testing, etc.
Roles & Responsibilities : Who does what ? like Testers, developers etc.
Testing tools & Standards
How will bugs be detect & resolved

1
Economics of Testing means the cost used in detection, fixing of bugs, cost of
failure (if bug is found after release then it cause financial cost, reputation,
customer complaints).
Balancing cost & Quality
Use risk-based testing (test critical areas more).
Automate repetitive tasks to save money & time.
Invest in good testing tools & skilled testers instead of fixing costly failures
later.
Testing as an Organizational issue :-
Testing isn’t just a Quality Assurance (QA) team responsibility – it affects the
entire organization.
Testing becomes a critical organizational issue when it's not integrated
effectively into the software development lifecycle. This can lead to delays,
increased costs, and ultimately, a lower quality product.
Why is Testing an Organization-Wide Concern?
High Costs & Delays : Finding bugs late in the project increases costs &
delays. Fix issues early.
Poor Product Quality : Not enough testing = more defects reach customers.
Unclear Roles & Responsibilities : If people don’t know who does what,
testing becomes chaotic. Clear roles = faster & smoother testing.
Resistance to Early Testing : Some teams avoid testing in the beginning,
leading to bigger problems later.
Inefficient Testing Process : Manually tracking bugs & poor communication
wastes time.
Testing should be planned, well-communicated, and given proper resources to
avoid costly mistakes.

Management Support in ST
If company leaders don’t prioritize testing, projects can face delays, high costs,
and poor product quality. Strong management support ensures:
Adequate Budget : Enough resources (people, tools, time) for testing.

2
Clear Testing Policies : Well-defined goals, roles, and responsibilities.
Improved Team Collaboration : Developers, testers, and managers work
together effectively.
Encourage Early Testing – Testing should start at the beginning of
development.
Invest in Automation – Saves time and reduces human errors.
Promote a Quality Culture – Make testing everyone’s responsibility, not just
QA’s.
Provide Training – Keep testers updated with new tools and techniques.
Use Metrics & Reports – Track testing progress and make informed decisions.

Key Steps of Testing

Defining objectives i.e. what do we want to achieve (bug-free soft. ,

security compliance etc).
Creating a test plan like outlining what, how, when, who will perform
testing.
Set up testing Environment .
Design test cases (detailed test scenarios to chk software’s diff. parts).
Execute Tests.
Track and Fix Bugs.
Review & Improve.

Effective & Effective Testing guidelines

Start testing early : Detecting bugs in early stages saves time & money.
Follow a structured approach : Use a Test plan.
Prioritize test cases : Focus on high-risky areas first.
Log & test bugs properly with tools like JIRA, Bugzilla, TestRail.
Continuously improve the process : Learn from past mistakes.

3
Workbench
Workbench concept is a structured approach which divides testing activities into
various stages. Each stage has inputs, outputs, tasks.
Stages:
Input : Test plan, Requirement, Test cases.
Process : Execute test tasks, log defects.
Output : Test reports, defect logs.
Review : Ensure all tests are completed , analyse results.

The workbench concept ensures a step-by-step, systematic approach to testing,

making it more organized and efficient.

Every project has unique needs, so the testing process should be customized to
fit. For ex : A banking app needs strong security testing, while a gaming app
may need performance testing.

Process preparation checklist

Before starting testing, certain steps must be completed to avoid mistakes like
preparation of test plan , test environment , roles etc ready. Without proper
preparation, testing may fail due to missing data, incorrect setup, or unclear
objectives.
Software testing techniques
Dynamic Testing
Dynamic Testing is type of software testing which involves the
software (whose testing is going on) which is executed to find the
defects.
For Ex : It’s like driving a car to check if everything works, rather than just
inspecting the engine and manuals.

4
Dynamic testing helps find real-time issues like crashes, incorrect outputs,
performance logs. Ensures the software works as expected in different
environments and Identify runtime errors.
Blackbox Testing
In this, the tester doesn’t look at the code, focus on what system does. It’s used
for UI, database, api testing etc.
Black Box Testing is like testing a vending machine, You press buttons and
check if the right product comes out, without knowing how the machine works
inside.
Since Testers don’t see the internal code, they depend on some techniques based
on inputs and expected outputs like Boundary Value Analysis (Test at the
edges where err are most likely) , Decision Table Testing (when multi-
conditions affect the output) , State Transition Testing , Error Guessing etc.
Whitebox Testing
In this, Testers looks at the internal code & test its logic. It requires knowledge
of the internal code. It is used to check loops, conditions, and logic.
White Box Testing is like checking the machine's internal wiring to ensure each
button is correctly connected.
He checks : Every possible execution path tested, Loops so that he find infinite
loops or boundary errors.
Both Black & White box testing are important for a high quality product.

5
Validation ensures the software meets user expectations and business needs.
Functional Validation : Checking if features work as expected.
User Acceptance Testing (UAT) : Final testing before release by actual users.
Regression Testing

Whenever code is changed, regression testing ensures new changes don’t break
old features. It’s done after bug fixes , adding new features , performance
testing. For ex : A company updates its payment system. Regression testing
ensures past transactions still work correctly.

UNIT - 2