Test Program Generator
Running the ProgGen
The program generator is launched via the Origen generate command, see the command line help to get details of the most up to date options:
origen program -h
As this is such a commonly used command it has a short cut alias:
origen p -h
The generator can be run on a single file:
origen p program/probe/sort1.rb
or it can be run on a whole directory:
origen p program/probe
Program list files can also be used, by convention these should be kept in the list directory
and should have the extension
origen p list/program/production.list
Here is an example of a list file:
# List files can be commented like this # Simply list the name of the files that you would use on the command line program/probe/sort1.rb program/probe/sort2.rb # List files can also call other lists ft.list
The generated files will be put in whatever directory
is returned by the
config.test_program_output_directory attribute in
Submit to the LSF by appending
-l and optionally interactively
wait for completion:
origen p list/program/production.list -l -w
Everytime Origen generates a file it will check to see if it has generated it before, and if so it will compare the current version to the previous version and alert if there is a difference. This can be used to check for regressions when making changes that you don’t want to affect the output, or to verify that the change is what you intended in cases where you are intentionally modifying the output.
The diff is a smart diff and will not care about any changes to comments, only about changes that will affect the file’s operation.
In the case of a difference being found Origen will automatically present you with the diff command to run if you want to view the change.
To accept changes or to start tracking the differences in a file (or files) run the following command after generating:
origen save all
If you start writing your own commands you may want to launch the generator from Ruby, do that as follows:
Origen.app.runner.launch action: :program, files: "list/program/production.list"
This can be combined with Target Loops to run the generator for multiple targets.
A generate job can also be posted to the LSF by supplying the same options that you would use on the command line like this: