Skip to main content

Scope: In Scope vs Out of Scope

 

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)
Follow on LinkedIn
Labels:

Comments

Post a Comment

Popular posts from this blog

Understanding Mistakes in Software Development: Errors, Defects, and Bugs

  Every software team uses the words “error,” “defect,” and “bug,” often interchangeably. But there’s real power in knowing exactly what each term means—and when it applies   1. Mistakes by Phase Phase What You Find What It’s Called Requirements & Design A mistake in the design or plan that doesn’t meet what stakeholders want. Defect Coding A coding or logic mistake in source code Error Testing & Execution An observable malfunction occurring during software execution or testing. Bug  🐞 1.1 Defect A defect is any flaw or mismatch in your requirements or design artifacts. It exists before any code runs. Example: You document “Users must enter a 4-digit PIN,” but stakeholders actually needed 6 digits. That spec mismatch is a defect . 1.2 Error An error is a mistake made while coding —a typo, wrong opera...
Post a Comment
Read more

What Is a Feature Flag?

  A feature flag (also known as a feature toggle) is a powerful software development technique that allows developers to enable or disable specific functionality in an application without changing the code or redeploying the software. 🧠 Core Concept Feature flags act like switches embedded in your codebase. They control whether a feature is active or inactive at runtime. This lets teams test, release, or hide features dynamically. 🚀 Benefits Safe Deployments : Deploy code with features turned off, then activate them when ready. A/B Testing : Roll out features to a subset of users to gather feedback. Quick Rollbacks : If something breaks, just flip the flag off—no need to revert code. Continuous Delivery : Decouple feature releases from code deployments for smoother CI/CD pipelines. User Segmentation : Tailor experiences for different user groups. 🧩 Types of Feature Flags Type...
2 comments
Read more

Test Data Design Techniques with Examples

  ✅ 1. Equivalence Partitioning (EP) What it is: Divides input data into partitions of equivalent data from which test cases can be derived. The idea is that if one value in a partition works, all others will too. Example: If a form accepts ages from 18 to 60: Valid partitions: 18–60 Invalid partitions: <18 and >60 Test cases: One value from each partition: 25 (valid), 17 (invalid), 61 (invalid) When to use: When input data can be grouped into ranges or categories. ✅ 2. Boundary Value Analysis (BVA) What it is: Focuses on values at the edges (boundaries) of input ranges, where defects are most likely to occur. Example: For an input field that accepts values from 1 to 100: Test boundaries: 0, 1, 2 and 99, 100, 101 Test cases: 0 (just below), 1 (lower boundary), 2 (just above) 99 (just below), 100 (upper boundary), 101 (just above) When to use: When input fields have defined minimum and maximu...
Post a Comment
Read more