Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
should
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • vidjil
  • should
  • Issues
  • #36

Closed
Open
Opened Mar 26, 2019 by Mikaël Salson@mikael-sOwner

Interleaving commands and tests

When interleaving commands and tests we (may?) want that the tests are performed only on the state reached so far and not after launching all the commands in the should file.

An example of what such a test could look like:

dir=$(mktemp -d)
ls $dir

$ Check that directory is empty
0:.

touch $dir/file
ls -1 $dir

$ Directory should now contain file `file`
1:file

rm -f $dir/file

$ Directory should be empty again
0:.

rmdir $dir
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
2.0.0
Milestone
2.0.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: vidjil/should#36