Judges over a Factbase Executor

A command line tool and a Ruby gem for running so called judges against a factbase.

Every "judge" is a directory with a single .rb file and a number of .yml files. A script in the Ruby file is executed with the following global variables available to it:

$fb — an instance of Factbase, where facts may be added/updated;
$loog — an instance of Loog, where .info and .debug logs are welcome;
$options — a holder of options coming from either the --option command line flag or the .yml file during testing;
$local — a hash map that is cleaned up when the execution of a judge is finished;
$global — a hash map that is never cleaned up;
$judge — the basename of the directory, where the .rb script is located.

Every .yml file must be formatted as such:

before:
  - abc
category: slow
runs: 1
skip: false
input:
  -
    foo: 42
    bar: Hello, world!
    many: [1, 2, -10]
options:
  max: 100
expected:
  - /fb[count(f)=1]
after:
  - first.rb
  - second.rb

Here, the input is an array of facts to be placed into the Factbase before the test starts; the options is a hash map of options as if they are passed via the command line --option flag of the update command; and expected is an array of XPath expressions that must be present in the XML of the Factbase when the test is finished.

The category (default: []) may have one or an array of categories, which then may be turned on via the --category command line flag.

The runs (default: 1) is the number of times the .rb script should be executed. After each execution, all expected XPath expressions are validated.

The before (default: []) is a list of judges that must be executed before the current one.

The after (default: []) is a list of relative file names of Ruby scripts that are executed after the judge ($fb and $loog are passed into them).

How to contribute

Read these guidelines. Make sure you build is green before you contribute your pull request. You will need to have Ruby 3.0+ and Bundler installed. Then:

bundle update
bundle exec rake

If it's clean and you don't see any error messages, submit your pull request.