Here’s the key difference between “In Scope” and “Out
of Scope” when writing a test plan—or any project plan:
🔍 In Scope
This defines what the team will work on or test.
It includes:
- Features
to be tested (e.g., login, checkout)
- Supported
platforms (e.g., mobile, desktop)
- Types
of testing (e.g., functional, security, UI)
- Expected
deliverables
Think of it as the “YES” list—things you’re promising to
cover.
🚫 Out of Scope
This outlines what the team won’t work on or test,
either because:
- It’s
not relevant to current goals
- It’s
being handled by another team
- It
might be deferred to a future phase
Scope Clarification
✅ In Scope
The following items are included in the testing efforts:
- User
functionalities such as registration, login, product search, and
checkout
- Payment
gateways: testing with credit/debit cards and digital wallets
- Notifications
via email and SMS
- Cross-browser
compatibility testing for Chrome, Firefox, Safari, and Edge
- Device
compatibility across mobile (iOS/Android) and desktop
- Performance
testing on staging environment under moderate load
❌ Out of Scope
The following are excluded from the current test phase:
- Compatibility
testing for legacy browsers (e.g., Internet Explorer)
- Integration
testing for third-party APIs not available in the test environment
- Full
localisation testing for non-English versions
- Penetration
testing or deep security audits (covered by separate team)
- Testing
under extreme load conditions (covered in a later phase)
Comments
Post a Comment