|
1 | 1 | ---
|
| 2 | + |
2 | 3 | # Job definitions used exclusively for unit testing.
|
3 | 4 | # They provide sufficient information to 'masquerade' as real jobs
|
4 |
| -# and are served up by the UnitTestDatabaseAdapter (found in the tests directory). |
| 5 | +# and are served up by the UnitTestAPIAdapter (in 'tests/api_adapter.py'). |
5 | 6 | #
|
6 |
| -# This offers bare-essential job definitions that are used to test |
| 7 | +# This offers bare-essential definitions that are used simply to test |
7 | 8 | # the workflow engine. It does not fully comply with the Job definition schema -
|
8 |
| -# only those that we need for testing the Workflow Engine. |
| 9 | +# only those parts that we need for testing the Workflow Engine. |
9 | 10 | #
|
10 |
| -# All jobs used for unit testing must be defined in this file. |
| 11 | +# All jobs used for unit testing are defined in this file. |
11 | 12 | #
|
12 |
| -# For each job you must provide: - |
13 |
| -# - Job command |
| 13 | +# The 'command' module is expected to be found implemented as a Python 3 module in the |
| 14 | +# 'tests/jobs' directory. So the smiles-to-file 'command' module ('smiles-to-file.py') |
| 15 | +# must be placed in the 'jobs' directory, and it must comply with the variables |
| 16 | +# defined here. |
14 | 17 | #
|
15 |
| -# The command is meaningless as the job that is run is expected to be |
16 |
| -# a Python 3 module called <job>.py in the tests/jobs directory. |
17 |
| -# So a nop job would have a corresponding Python module called nop.py. |
18 |
| -# The test instance_launcher module will run the job. |
| 18 | +# Jobs are executed in the 'project-root/project-00000000-0000-0000-0000-000000000001' |
| 19 | +# directory that is created (and wiped) by the UnitTestInstanceLauncher |
| 20 | +# (in 'tests/instance_launcher.py'). |
19 | 21 |
|
20 | 22 | collection: workflow-engine-unit-test-jobs
|
21 | 23 |
|
|
0 commit comments