Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
S
subplot
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Lars Wirzenius
  • subplot
  • Issues
  • #116

Closed
Open
Opened Nov 07, 2020 by Daniel Silverstone@kinnisonMaintainer

Subplot documentation needs to explain scenario language more effectively

When discussing Subplot with a user, when they described putative scenarios they often used the term 'if' and assumed that the scenario language included some kind of conditional operation. Also there was slight confusion around when vs. then, and given vs. when.

It would behove us to improve the documentation around the scenario language keywords, perhaps by means of better examples or discussions of which keywords are appropriate for any given step.

Assignee
Assign to
Iteration starting 2021-03-13
Milestone
Iteration starting 2021-03-13
Assign milestone
Time tracking
None
Due date
None
Reference: larswirzenius/subplot#116