|Alois Mahdal a00e180c26 Fix maintainer c/p error||5 years ago|
|src||5 years ago|
|Makefile||5 years ago|
|README.md||5 years ago|
|mkit.ini||5 years ago|
This is an independent test suite for fictional compoment 'demo'. The suite is intended to be reference example for JATS - Just A Test System.
JATS defines test suite format, which is a directory tree consisting of individual tests. These individual tests can in principle be implemented in any language, but for now shellfu-bash-jat is the only available library.
Direct dependencies are:
All of the above have their own dependencies, so if you want to install everything manually, follow instructions on their pages.
Most tests should work without installation. That is, just cloning this repo should be enough. OTOH, in production environment--if you want to ensure integrity of the tests and eg. have them be able to report their own version, instaling the suite is recommended.
Manual installation consists of:
make sudo make install
yum install yum-plugin-copr yum copr enable netvor/shellfu yum copr enable netvor/jats yum install jats-demo jattool
Note that older systems like RHEL-6 don't have the COPR plugin, so you will need to add repositories manually. There's a script in GitHb Gist to help you with this step on CentOS-6 & RHEL-6.
Also note that in order to minimize dependencies on testing machine, install just jattool-minimal package, which contains only the bare minimum needed for running tests.
Sorry, but since author of the tools does not know how to create at least remotely proper Debian repository, .deb packages are available on-demand only. See Contact section in main README.
To show list of installed tests:
jattool tfind /usr/share/jats
Each JAT test is a directory, so above should give you list of directories: you
can then run any of them using
jattool runtest, eg.:
jattool runtest /usr/share/jats/suite/demo/foo
should give you something like this:
test.INFO: id: jats://my.example.org/foodept/barpkg//foo test.INFO: version: 0.0.1 session.START phase.START 'example test phase' test.INFO: CMD: true assert.PASS: true is still true assert.PASS: five is still greater than three assert.PASS: foo still ends with oo phase.END.PASS 'example test phase' session.FINALIZE.PASS
I won't go into details; I'll tell you just enough to get you started, but be aware that (mostly) everything is (mostly) documented and primary ways to get help (actually more like reference, but helps) using sfdoc tool, which should be on your workstation by now.
Tests normally only consist of one important file, named ... you guessed it... test. (There's also main.fmf, but that only contains meta-data, which is not even really used these days.)
$ tree src/api/binary_req src/api/binary_req ├── main.fmf └── test
So open that file: it's a Bash script with extra "enhancements": you'll see things like:
shellfu import jat shellfu import preupg shellfu import ... shellfu import xcase
Shellfu platform brings modularity to Bash, so the names above are names
jat is a module name. And you can get reference on the module
Since this is Bash, modules contain just functions and variables. And since Bash has no namespaces, an important convention for (almost) all modules is in place:
foomust be named by
foomust be named by
Eg. an initializing function from module bar would have to be called
NOTE: At the time of this writing, the test creation kit is not finished, so if you really need new test, you can just copy another one.
In order to avoid duplication of work and unnecessary frustration, take following steps:
Before you start, contact maintainer and inform them that you are planning to write a test. You can do this by filing an issue in Gitea repo or by contacting the maintainer directly.
Read Shellfu coding style; tests need to follow this.
Be aware that the JATS project is in early stage (
some (most?) pieces of coding style and conventions are not yet
written down. A more consistent documentation is expected to arrive