ST - Unit 2
ST - Unit 2
Risk Mitigation – Testing helps identify defects and failures early in the
development process when they are less expensive to fix. This reduces project risks
related to quality, security, performance, etc.
Confidence – Executing a well–planned software test strategy provides confidence
that the software works as intended before its release.
Compliance – Testing can ensure that software adheres to standards, regulations,
and compliance requirements. This is especially critical for safety–critical systems.
User Satisfaction – Rigorous testing from a user perspective can verify usability,
functionality, and compatibility. This increases customer/user satisfaction and
reduces negative impacts to an organization’s reputation or finances from poor
quality products.
Optimization – Testing provides vital feedback that can be used to continuously
improve software quality, user experience, security, performance and other product
attributes.
Cost Savings – Investing in testing activities reduces downstream costs related to
defects found post–release. It is much cheaper to find and fix bugs earlier in the
development cycle.
2. Representation SDLC stands for Software STLC stands for Software Testing
Development Life Cycle. Life cycle.
7. Different phases The various phase includes The various phase includes
in Software Development Life in Software Testing Life Cycle are
Cycle are as follows: as follows:
o Requirements Collection o Requirement collection or
o Feasibility Study System study
10. Coding phase In the SDLC coding phase, the In STLC, the QA team writes the
developer will start writing the code test scenarios to authenticate the
as per the designed document and quality of the product.
beginning of building the software.
11. Environment After writing the code, the Based on the prerequisites, the Test
Set up development team sets up a test team confirms the environment set
environment with the developed up. And do one round of smoke
product to validate the code. testing to ensure that the
environment is stable for the
product and ready for testing.
12. Testing Phase Once the environment has been set, Based on the test cases, the tester
the test engineer will perform will do one round of integration
various types of testing, such as and system testing.
Unit, Integration, While performing the testing, if
System, Retesting, Regression they encounter with any bugs, it
testing, and so on. will be reported and fixed after the
And the development team is also retesting.
involving to fixing the bugs and
report back to the tester.
13. Deployment/ In the SDLC deployment phase, In STLC, the Smoke and sanity
Product Release when we received sign-off from testing are performed in the
phase various testing teams, the production environment as soon as
application is deployed or installed the product is deployed.
in a production environment for real And the testing team will prepare
end-users. the test reports and matrix to
analyze the product.
14. Maintenance Once the product has been To check maintenance code
Phase deployed, the development team deployed, the QA team performs
includes support and release the regression suites.
updates.
15. Performed The SDLC phases are done before The STLC phases are completed
the STLC phases. after SDLC phases.
Deliverables
Test Strategy
It defines the scope, risks, quality criteria, testing techniques, resources, and timelines,
providing a strategic view of how testing will be conducted throughout the project.
Test Plan
The Test Plan is a detailed document that describes the testing approach, objectives, and
methodologies. It includes the scope of testing, roles, timelines and test schedule, resource
allocation, and test environment requirements.
Test data
Test Data in software testing provides the necessary input and configurations to execute tests.
It’s like the patient’s medical history, helping testers understand the software’s behaviour
under various conditions.
Test Data encompasses the input values, configurations, and scenarios used during testing.
Test Case Generation: In this software testing test case generation is nothing but
making different test cases which may cause error.
Test Case Execution: After the test case generation, real testing process begins.
This is the most prominent part of the testing process.
Result and Analysis: After the execution of the test case, its result is analyzed. It
includes the checking of the inconsistency in the expected output for the
generated test case.
Re-test: If the testing is failed then after the analysis once more all the above
steps are performed to test the system.