Software Testing: Software testing is a procedure to check whether software product matches to
expected as per requirements provided with defect free product delivery.
Responsibilities of tester: Tester should always make sure to get the keen understanding on the
requirement, changes on product if its enhanced project, testing components involved in the
requirement without a miss. While performing testing Tester has to identify errors or bugs, missing
requirements in the application or product.
Test Types: White box and black box testing
White-box: This testing will perform by tester who aware on the internal
structure/design/Implementation/code. Mostly this will perform by developers.
Black-box: This testing will perform by tester who is not aware on the internal
structure/design/Implementation/code. Mostly this will perform by testers.
Functional Testing
Unit Testing: This will perform by developer to test the unit of the program.it helps to the programmer
that the coded code is working properly.
Integration Testing: This testing performs by testers on the construction and design of the product.
Tester has to check that integrated code is working properly or not.
Smoke Testing: It’s the initial stage of testing to make sure that product application is working without
any region issues or platform issues to start functional testing.
UAT: Mostly UAT performs by end users and clients that who initiated or provided requirements to the
team.
Maintenance Testing:
Regression Testing: Regression testing performs by Testers to make sure that existing system is not
impacting to current system due to latest changes performed by Developers.
SDLC: Software Development Life Cycyle
Requirement:
1. Business Analyst collects the requirement from the Customer/Client as per the clients business
needs and documents the requirements in the Business Requirement Specification
Analysis Phase:
1. Define Product Requirement
2. Products to be developed, Key people involved in – Project Manager, Business Analyst, Senior
Members
3. Software Requirement Specification
Design Phase:
1. HLD – Architecture of the Software Product. Done by Senior Developers and architects
2. LLD – Done by Senior Developers. Describes How each and every component should work
Development Phase:
1. Code Development
Testing Phase:
1. Product Testing
Deployment:
1. Deploy the product into Product Environment
STLC:
Requirement Analysis
During this phase, test team studies the requirements from a testing point of view to identify the
testable requirements.
The QA team may interact with various stakeholders (Client, Business Analyst, Technical Leads, System
Architects etc) to understand the requirements in detail.
Automation feasibility for the given testing project is also done in this stage. Activities
● Identify types of tests to be performed.
● Prepare Requirement Traceability Matrix (RTM).
● Automation feasibility analysis (if required).
Deliverables
● RTM
● Automation feasibility report. (if applicable)
Test Planning
Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and
would prepare and finalize the Test Plan. In this phase, Test Strategy is also determined.
Activities
● Detailed Requirements
● Preparation of test plan/strategy document for various types of testing
● Test tool selection
● Test effort estimation
● Resource planning and determining roles and responsibilities.
● Training requirement
● Dependencies
● Risks
Deliverables
● Test plan /strategy document.
● Effort estimation document.
Test Case Development
This phase involves creation, verification and rework of test cases & test scripts. Test data , is
identified/created and is reviewed and then reworked as well. Activities
● Create test cases, automation scripts (if applicable)
● Review and baseline test cases and scripts
● Create test data (If Test Environment is available)
Deliverables
● Test cases/scripts
● Test data
Test Environment Setup
Test environment decides the software and hardware conditions under which a work product is tested.
Test team may not be involved in this activity if the customer/development team provides the test
environment in which case the test team is required to do a readiness check (smoke testing) of the given
environment. Activities
● Perform smoke test on the build
Deliverables
● Environment ready with test data set up
● Smoke Test Results.
Test Execution
During this phase the testers will carry out the testing based on the test plans and the test cases
prepared. Bugs will be reported back to the development team for correction and retesting will be
performed. Activities
● Execute tests as per plan
● Document test results, and log defects for failed cases
● Map defects to test cases in RTM
● Retest the Defect fixes
● Track the defects to closure
Deliverables
● Completed RTM with execution status
● Test cases updated with results
● Defect reports
Test Cycle Closure
Testing team will meet , discuss and analyze testing artifacts to identify strategies that have to be
implemented in future, taking lessons from the current test cycle. The idea is to remove the process
bottlenecks for future test cycles and share best practices for any similar projects in future.Activities
● Evaluate cycle completion criteria based on Time,Test coverage,Cost,Software,Critical Business
Objectives , Quality
● Prepare test metrics based on the above parameters.
● Document the learning out of the project
● Prepare Test closure report
● Test result analysis to find out the defect distribution by type and severity.
