• Test Experiments
  • Test 01
  • Test 02
  • Test 03
  • Test 04
  • Test 05
  • Test 06
  • Test 07
  • Test 08
  • Test 09

Test Experiments¶

• Here are some focused self-contained test experiments, which you could use to test some of OMF functionalities.

• IMPORTANT: these tests experiments are for the 5.3 OMF release, which currently under development, and which is available directly from git or in the 'testing' package section.

• For example, you could run these experiments after making some change in the source code or you testbed setting, to check that your the EC and RCs still function correctly (for the function under test).

• These tests should complement any unitary tests, as they allow to also check that control and data communications with PubSub server and the other entities is actually performed, and in the right sequences.

• Within each of the tar.gz test file below you will find:
  • the experiment script: exp.rb
  • the omf exec command used to run the experiment: run.txt
  • an example standard-out output of omf exec, which you should see: result_stdout.txt
  • an example of the SQLite3 database that you should get at the end (if OML-enabled application are used): result_database.sq3
  • an example of the final EC log file: result_ec_log.txt
  • an example of the final XML state file from the EC: result_ec_state.txt
  • one or more examples of the final RC log file: result_rcX_log.txt

• You can use these example result files to compare with your result and check for correct experiment execution

• You can also run these experiments directly from the EC's repository: omf-5.3 exec test:exp:test01 -- --res1 omf.nicta.node1

Test 01¶

• test01-basic.tgz

• 1 node in 1 group running 1 exec command for an already installed application

• Testing that:
  • Initial communication (ENROLL + ALIAS) is happening between the EC and a RC on a real resource
  • Basic Group manipulation works
  • Use of EXECUTE for an application already installed on the resource
  • Correct processing of RC's events returned to the EC

Test 02¶

• test02-groups.tgz

• 2 nodes in many groups running many exec commands for already installed applications

• Testing that:
  • Multiple group manipulation works
  • Events/Outputs from multiple applications running are processed correctly at RCs and EC

Test 03¶

• test03-wifi-otg.tgz

• 2 nodes in 2 groups running already installed OTG and OTR (over WIFI) with OML support

• Testing that:
  • Use of an existing Application Definition by an Experiment works (thus also checking that repository scripts is there)
  • OTG and OTR works
  • OML data collection works (basic 'interval' and 'samples' filter)
  • Static Experiment Properties works
  • Configuration of atheros madwifi interfaces on the resource works
  • Correct function of EC/RC CONFIGURE commands

• In addition to the OMF software being installed, this test requires the OML, OTG /OTR software to be installed, and the resources to have a WIFI atheros card

Test 04¶

• test04-dyn-prop.tgz

• 2 nodes in 2 groups running already installed OTG and OTR (over WIFI) with OML support

• Testing that:
  • Dynamic Experiment Properties works

• In addition to the OMF software being installed, this test requires the OML, OTG /OTR software to be installed, and the resources to have a WIFI atheros card

Test 05¶

• test05-custom-app.tgz

• 1 node in 1 group running a custom user-defined application

• Testing that:
  • in-file and custom Application Definition (defApplication) works
  • PM Install works
  • all the possible bindings between the application arguments and OMF works
    • boolean, string, integer
    • ordered or not, use of mnemonic or not, use of option name or not

• In addition to the OMF software being installed, this test requires the OMF Experiment Controller (EC) to be accessible to the experiment's resources (i.e. not behind a firewall)

Test 06¶

• test06-apt-install.tgz

• 1 node in 1 group running an existing 3rd party application, installed via APT

• Testing that:
  • APT Install works
  • argument binding for existing application works

• In addition to the OMF software being installed, this test requires the experiment's resources to have correctly configured and accessible APT repositories.

Test 07¶

• test07-rpm-install.tgz

• 1 node in 1 group running an existing 3rd party application, installed as an RPM via 'yum'

• Testing that:
  • RPM Install works
  • argument binding for existing application works

• In addition to the OMF software being installed, this test requires the experiment's resources to have correctly configured and accessible RPM repositories.

Test 08¶

• test08-upload.tgz

• 1 node in 1 group, which receives a binary data file during the experiment

• Testing that:
  • upload of arbitrary data file to an experiment's resource works

• In addition to the OMF software being installed, this test requires the OMF Experiment Controller (EC) to be accessible to the experiment's resources (i.e. not behind a firewall)

Test 09¶

• test09-wired-otg.tgz

• 2 nodes in 2 groups running already installed OTG and OTR (over a wired network) with OML support

• Testing that:
  • Use of an existing Application Definition by an Experiment works (thus also checking that repository scripts is there)
  • OTG and OTR works
  • OML data collection works (basic 'interval' and 'samples' filter)
  • Static Experiment Properties works

• In addition to the OMF software being installed, this test requires the OML, OTG/OTR software to be installed
• This test is similar to test 03, but without the wireless configuration part.
• Currently OML, OTG/OTR are only available as Debian/Ubuntu packages. RPM package will come soon.

---