Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests: add example feature files #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

tests: add example feature files #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions tests/log-messages.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Tests for the expected workflow log messages

Feature: Log messages

As a researcher,
I want to be able to see the log messages of my workflow execution,
So that I can verify that the workflow ran correctly.

Scenario: The compilation step has produced the expected messages
When the workflow is finished
Then the engine logs should contain
"""
Publishing step:0, cmd: g++ -v -O3 -o dimuonSpectrum dimuonSpectrum.C `root-config --cflags --libs`
"""

Scenario: The data analysis step has produced the expected messages
When the workflow is finished
Then the job logs for the "run" step should contain
"""
Events with exactly two muons: pass=31104343 all=61540413 -- eff=50.54 % cumulative eff=50.54 %
Muons with opposite charge: pass=24067843 all=31104343 -- eff=77.38 % cumulative eff=39.11 %
"""
And the job logs for the "run" step should contain
"""
Info in <TCanvas::Print>: pdf file dimuonSpectrum.pdf has been created
"""
And the engine logs should contain "Publishing step:1, cmd: ./dimuonSpectrum"
19 changes: 19 additions & 0 deletions tests/run-duration.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Tests for the workflow execution duration time

Feature: Run duration

As a researcher,
I want to verify that my workflow finishes in a reasonable amount of time,
so that I can stay assured that there are no unusual problems with computing resources.

Scenario: The workflow terminates in a reasonable amount of time
When the workflow execution completes
Then the workflow run duration should be less than 5 minutes

Scenario: The compilation step takes a reasonable amount of time
When the workflow is finished
Then the duration of the step "compile" should be less than 3 minutes

Scenario: The step in which the analysis is run takes a reasonable amount of time
When the workflow is finished
Then the duration of the step "run" should be less than 3 minutes
18 changes: 18 additions & 0 deletions tests/workspace-files.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Tests for the presence of files in the workspace

Feature: Workspace files

As a researcher,
I want to make sure that my workflow produces expected files,
and that all the necessary input files are present in the workspace,
so that I can be sure that the workflow outputs are correct.

Scenario: The workspace contains all the relevant input files
When the workflow execution completes
Then the workspace should include "dimuonSpectrum.C"

Scenario: The analysis produces the expected output file
When the workflow is finished
Then the workspace should include "dimuonSpectrum.pdf"
And the size of the file "dimuonSpectrum.pdf" should be between "180 KiB" and "190 KiB"
And all the outputs should be included in the workspace