Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
T Test Specification
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Simulation
    • PProposals
  • Study Group
  • Test Specification
  • Issues
  • #5

Closed
Open
Created Sep 23, 2020 by Andreas Rauschert@Andreas.Rauschert

Definitions of test case and scenario

The proposal defines test scenario as "What to be tested?" and Test Case as "How to be tested?".
This is not according to the definition of a test case from test engineering domain (see e.g. here). It contains input, SUT, Init conditions, Variants, test procedure and expected results.
From my POV a scenario is not more than a procedure. It can be part of a test case. Therefore I think the sentence "Test Case: Is derived from a scenario" is also misleading. It´s the other way round.
A scenario cannot define what to be tested. The SUT is what to be tested and is out of scope for the scenario.
I would propose to replace these definitions of scenario and test case by definitions from test engineering and e.g. the OSC 1.0 User Guide (chapter 1.3 "Scope").
Otherwise the proposal will introduce more confusion than clarify.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking