Please enable JavaScript.
Coggle requires JavaScript to display documents.
Janitorium test plan baseline - Coggle Diagram
Janitorium
test plan baseline
Goals
Prevent issues
Speed up software development
Get early working prototypes
Release products in time with good quality
Scope
In Scope
requirement testing
test env preparation
test data preparation
System testing
(positive and negative)
Android devices
Apple devices
admin interface
UI/UX
Integration testing
Apps and devices to the server
Access control
OSM Maps
Custom Maps
Security testing
Performance testing
Test Automation
Out of Scope
Localization testing
Unit testing
Approach
(Strategy)
Shift Left
Test Requirements
Review SW design
Configure test env
Classic
Functional
System testing
Test Data preparation
Integration testing
Report frequently
Non Functional
Usability (UI/UX)
during system test
Performance
once before UAT
Security
During system test and during UAT
Reliability
Withing performance testing
Test Design First
Test automation
Stable features only
Focus on mobile apps
Entry Criteria
Static Testing
Documents created
Document approved
Dynamic Testing
Env prepared
Unit tests coverage 15% achieved
Software deployed
Devices provided
Data created
Automation
Feature stable for 3 sprints
Exit Criteria
Customer request
Quality Gate
All tests executed
0 open blockers
0 open criticals
up to 5 open majors
Resources
Test Lab
Separate network
Access control devices
SUT server
Devices
Laptop
Apple
iPhone 14
iPhone 15
iPad 10 2021
Android
Galaxy S21
Galaxy Tab 8 2021
Xiaomi 11 lite
Software
Postman
Swagger
Jira
Browser MS Edge
People
2 Middle QA engineers <names>
Progect Manager <name>
Product Owner <name>
DevOps <name> / part time
Test automation engineer <name>
Performance testing engineer <name> / part time
UX Designer <name> / part time
Time
01.01.2001 - Kickoff
01.02.2001 - Design agreed
01.03.2001 - Prototype deployed
01.06.2001 - UAT
Risks
Job for milestones not done yet
track progress frequently, red flag early. Ask for more time or reduce the scope
Env not available
call the DevOps
Switch to requirements review while waiting
The engineer is not available
share knowledge weekly, write howtos
Buy health insurance
Requirements are changed frequently
Track the number of changes, and red flag issues early.
Timezone gap
Prepare questions in advance
Have sync meetings during a common time
3rd party not available for integration
estimate effort for mock creation, implement mocks
reduce testing scope, warn stackeholders
Softweare performance is below requirements
Find and reduce bottlenecks
Request more powerful hardware
Deliverables
Checklists
Test Reports
Bug reports
Test Plan
Performance report
Go/Nogo decision