-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
basic integration test #55
basic integration test #55
Conversation
🤖 Merge 8.3.x-sync into master
🤖 Merge 8.3.x-sync into master
🤖 Merge 8.3.x-sync into master
🤖 Merge 8.3.x-sync into master
An attempt to produce a slicker integration test foundered upon cylc#6189 which prevents the onward triggering of flows in simulation mode. 😞 |
'cylc set ${CYLC_WORKFLOW_ID} //1/good --flow=2\n' | ||
'cylc trigger ${CYLC_WORKFLOW_ID}//1/first --flow=2' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running actual bash scripts including Cylc commands makes this a functional test, not an integration test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be possible to test this using start
rather than run
by calling:
schd.pool.set_prereqs_and_outputs
(to set the output in flow 2)schd.pool.force_trigger_tasks
orschd.pool.get_or_spawn_task
(to spawn the upstream task in flow 2)schd.pool.spawn_on_outputs
(to test the spawning of downstream tasks from upstream outputs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give it a go. I was trying that approach when I ran into problems with sim mode, but actually, just not running in sim mode....
3277917
to
f5cf97d
Compare
c0ac01e
to
8d6b02a
Compare
THis has been left behind and is now stale. Hilary has written a better test since. |
This is barely an integration test: It runs the entire workflow which makes all the changes to itself.
I'm feeling my way towards a much more integration-style test, but it's not working yet.