1. Manual Testing
Automation Test plan
Release procedure
Agile Scrum
Behaviour Driven Development(BDD)
Test and Release Strategy

2. Here we document each and every step need to be followed to execute the tests. After executing
tests we should update the status of the test every time you execute the tests whether it is passed
or failed
Here we document no of scenarios available for a feature. We can map test coverage in this
document
Here we include all the features we want in the application and we keep on updating this
document with the new functionality (or) Enhancements requested by the stack holder.
Manual Testing
Feature_Id Feature Feature Description
Test Feature
Traceability
Scenarios
Feature_Id Feature Feature Description Scenario_Id Scenario Description
Scenario_id Scenario Description Pre-Requisition Steps to Perform Data Required Expected Results actual results Status defect id Comment

3. Test Running
Mobile Testing
Headless trigger
Cross Browser
CI Jenkins
Test Results
Email Notifications
Time Based Triggering
Dev Testing on local machine
Analysing Scenarios
Analysing Acceptance
criteria
Frame Work Setup
Automation Test Plan
Test creation

4. Release procedure
Tag
Test on Dev
Environment(Sanity)
Regression Testing on
Test Environment
New functionality (or)Enhancement
& Exploratory Testing on Test
Environment
Front end design and
layout check
Deploy to pre- live
Monitoring logs
[Graylog & Nagios]
Release into production
& final check
Review after release, 1 hr
review & 24 hrs review
Trunk
Results
p
a
s
s
fail

5. This gives the full view of the work flow. If there is any Bug raised in QA then the
ticket need to be given high priority and it need to be looked after as the first thing.
Agile Scrum
Scrum Board
Sprint
Backlog
User Story Review Development Peer review QA Done Released
Burndown Chart
0
0.5
1
1.5
xx/xx/xxxx xx/xx/xxxx xx/xx/xxxx xx/xx/xxxx
Date
WorkRemaining

6. BDD(Behaviour Driven Development)
This gives the full view of the work flow. Here in BDD we Analysis the user story
and document all the possible scenarios for a user story before developing. It is
developers duty to make sure this scenario’s passed before it goes live.
BDD Board
Sprint
Backlog
User Story
Review
QA(Feature & scenario
Documentation)
Development Peer review Done Released
Burndown Chart
0
0.5
1
1.5
xx/xx/xxxx xx/xx/xxxx xx/xx/xxxx xx/xx/xxxx
Date
WorkRemaining