Basics about Jobs

In Scade One product, jobs are used to describe the calls to batch tools (code generation, model check, simulation and test execution).

What Are Jobs?

A job describes the inputs and the configuration to call a tool. A command line can be generated from the configuration of the job.

A job is contained inside a project: it can use modules inside that project and all its dependencies. You simply set the input module and the root operator; the other modules are automatically added using the dependencies between the modules and the projects.

Types of Jobs

The following jobs are available:

Job TypeDescription
Code generationGenerates C code from a model:

  • Inputs: root operator(s), options, and command-line arguments

  • Output: generated code asset in the jobs/ folder of the project directory

Model checkChecks that a model is correct, without generating code

  • Inputs: root operator(s) and command-line arguments

  • Output: none

SimulationNon-interactive or debug mode from a test harness:
  • Inputs: test harness, command-line arguments

  • Output: simulation trace in the jobs/ folder of the project directory

Test executionNon-interactive mode from at least one test harness defining an oracle or/and an assert
  • Inputs: test harness, command-line arguments

  • Output: result file in the jobs/ folder of the project directory