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
  • #4

Closed
Open
Created Sep 23, 2020 by Oliver Philipp@oliver.philipp

Scenario is not the SuT

In section 2.2. we find "In this section we’ll try to detail how a scenario should be tested.". It is important to distinguish between the System under Test (SuT) which is the entity to be tested. In order to test the SuT, scenarios (as defined by OpenScenario) are being executed, and finally the result of the test (e.g. passed/failed) is derived. Therefore, a scenario is not at all tested.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking