Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Fixed obsolete TDK requirement I forgot to bump TDK requirement range embedded in packaging templates for suites. That is, suites built with jattool-tdk of 0.2.* would require jattool-tdk of 0.1.*.

Overview of changes: * Updated dependency range on shellfu-bash-jats

Overview of changes: * Replaced most of discovery code with shellfu-bash-jats The ported code has been cleaned up and some parts rewritten, getting much better performance. * Removed jattool-qrun from public CLI It was never intended to be normally run by anyone, really. * Fixed jattool-runid unable to ever find any run

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Small jatdoc improvements

Overview of changes: * Fixed `indent()` call to use older keyword name Turns out the keyword was named `indentfirst` pre-2.10, so eg. on RHEL-7 and older, this will cause traceback. Luckily `indentfirst` still works on newer systems, so we're going to stick to it as long as we can.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * jatdoc will now include section with all found WAIVER/'s * Added support for extract test code link Jinja templates now contain test code link if provided by log.yaml. * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep. * Updated MKit for test suites and jattool to v0.0.40

Overview of changes: * Reworked testdoc URL operations Now the testdoc URL is computed by jat.sh during test initialization, ie. it can be printed to console and saved to log.yaml. Ie. the base URL shall be set during run, and the owner of the variable is now `jat.sh`. * Moved test id parsing to new shellfu-bash-jats module Shared code related to JATS spec should now be in a separate library. To avoid cyclic SRPM level dependency via shellfu-bash-jat, the new shellfu-bash-jats is distributed separately. * jatdoc's suite.md will not use only relative path as section name Using whole test id makes for a rather ugly doc.

Overview of changes: * Removed 'v' prefix from jattoc version directory

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep. * Fixed outdated docstring

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Improved accuracy final status warning * Added _errors private template to help with error escalation * TDK will now preserve modes of files in test suite

Overview of changes: * Addded support for test documentation auto-generation Test suite maintainets can now add test documentation to their `test` scripts in form of Markdown based docstrings as described by Shellfu coding style. https://netvor.info/notes/shellfu-style.html If they decide to do so, calling `make jatdoc` (ideally after `make release`) will compile `suite.md`, which can be converted to HTML5 and published on a web server. Documents produced this way can be easily linked to test results by providing base URL of the web server as environment variable when using `jattool export`. For example, given a test suite for 'mypkg' at version 0.0.1 running test sanity/smoke, export command: JATTOOL__TDBASEURL=https://example.com/jatdoc/ jattool export /path/to/log.yaml will automatically include links to https://example.com/jatdoc/mypkg/v0.0.1/suite.html#sanity/smoke where `v0.0.1/suite.html` is direct conversion of `jatdoc/v0.0.1/suite.md` as generated by `make jatdoc`. * Updated TDK file layout to enable using TDK Makefile as entry point This is the non-compatible change; it will require projects to switch to new path in their Makefile: include /usr/share/jattool/tdk/Makefile However, this change enables more extensions to be accessed via Makefile, almost eliminating need of future non-compatible changes. * Moved to branch naming scheme ...where latest released version is tracked by branch 'latest', not 'last'. * Updated MKit for test suites and jattool to v0.0.39

Overview of changes: * Updated MKit to v0.0.38 New version adds 'to <new version number>' to 'Bump version' commit messages. * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Added support for "zero plan" meaning all tests Every test suite now automatically contains plan that is specified by suite ID followed by percent sign. This plan means all tests from the suite. * Added support for local enumerators (experimental) Test can now include extra script to enumerate (promise) cases that the test is able to run. * Improved export facility User can now specify extra template search paths, filename template can refer to subdirectories and some safety improvements. * Added guarranteed one-line summary StringData.oneline() * Added missing newline at the end of 'txt' reports * Added load_last() utility function to load last run easily * Enabled colors and verbosity by default * Smaller code cleanups and improvements

Overview of changes: * Fixed false positive when looking for JATS tests When searched directory contained sub-directory named 'test', it would produce false and invalid positive.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Abandoned "session" term in favor of "run" The term "session" is confusing; "run" should be pretty obvious in most contexts. * Added plaintext export templates * Fixed infinite loop on double PHASE.END

Overview of changes: * Switched to own spec file globals for Python None of disrro-provided globals were reliably accessible across distros (we want to support RHEL-6 to RHEL-8 as well as recent Fedoras), so here we are. * Smaller cleanup in spec file

Overview of changes: * Split-off jat.py as separate Python2 package python2-jats The Python JATS interface is now under `jats.session`. * Ensure every assert always has id Asserts did not inherit testid as their caseid. Since Case()'s are just groups of asserts with same id, it was possible that if asserts had not specified caseid (which is almost guarranteed as caseid's are very optional), asserts would end up unreachable via case list. * Smaller meta-data cleanups and maintenance

Overview of changes: * Updated for shellfu-bash-jat v0.0.15 New JAT library slightly changes format of phase by replacing the concept of 'name' with 'hint'. This is more consistent with assert level. * Fixed slocate() reporting empty result as finding * Adapted PyYAML Requires name for RHEL-8 * Resolved YAML deprecation issue by using yaml.safe_load_all() * Added visual delimiters to make output from runplan easier to read

Overview of changes: * Fixed exception when loading quoted string

Overview of changes: * Added basic support for planning Plans have form jats://domain/dep/pkg//%planname, and are realized by special scripts included in test suite (%planname would be under _jats/plans/planname). The interface is specific command runplan, but in future these will be probably merged with runtest. * Updated string storage and presentation for shellfu-bash-jat v0.0.14

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Enabled adding params right after test id * Bumped jat library requirements

Overview of changes: * Added support for RELIC.* event types * Added support for passing parameters to test * Bumped jat library requirements

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Fixed c/p error in debian install list * Fixed small error handling error

Overview of changes: * Bumped jat library requirements

Overview of changes: * Bumped jat library requirements For safety reasons we keep jattool and shellfu-bash-jat versions in lockstep.

Overview of changes: * Consolidate and improve jat2rl format with regards to API New API gives more control to the beakerlib part.

Overview of changes: * Added CASEIDs to exports * Added "generated by" footers to export templates * Enabled tab completion features * Packaging cleanups

Overview of changes: * Updated MKit to safer version New MKit version brings removes problematic grep calls; see https://github.com/koalaman/shellcheck/issues/1342 for more details.

Overview of changes: * Fixed TypeError when collecting CASEIDs * Lints now won't be duplicated in report * Updated for Saturnin v0.5.0+ * Smaller packaging improvements

Overview of changes: * Added cases to Python Session model Just in the session model, but nor used in Jinja templates. * Bumped Shellfu/Bash/JAT version to released one

Overview of changes: * Disabled inheriting of Saturnin envvars Turns out that inheriting environment variables breaks whatever app that is called from another app.

Overview of changes: * Added support for adding fmf-0.5+ meta-data trees JATS suites now can (or have to, because .spec file is still kinda dumb) include fmf tree. * Updated docs after batch of hosting changes

Overview of changes: * Applied proper HTML escaping Ie. HTML content and similar should show up properly in messages et al. * Switched message passing in translator functions to via stdin Just like embedded data is already passed, pasing via stdin avoids the problem that Jinja2 can't escape for Bash. * Ensure YAML is always read as utf-8 * Fixed crash when adding lint to EventTree itself For example, missing phase end could trigger this. * Codebase maintenance

Overview of changes: * Fix jinja2 requirement for RHEL-7 Turns out that RHEL-7 also calls it python2-jinja2 * Updated MKit for test suites to v0.0.35

Overview of changes: * Added Jinja2 template for beakerlib translate script Generates shell script that can be called from within beakerlib test to "re-enact" the JAT in beakerlib language. * Updated log data model with session and test identifiers * Added test id to HTML report title * Added missing PyYAML dependency * Codebase maintenance

Overview of changes: * Fixed dependency tree

Overview of changes: * Set release source and destination branches in skeleton * Added debugging around test execution

Overview of changes: * Fixed test discovery code Most of the code was broken; discovery by id, version printing... Now it's still embarrassingly slow, but at least it somewhat works. * Updated MKit for jattool and test suites to v0.0.34

* Updated parser, Jinja templats and more for newer shellfu-bash-jat * Added meaningful content to README.md * Added support for showing test/suite version * Changed 'jats' term to 'id' for jats:// test and suite ids * Ensured proper test status from runtest matches qrun (and * Split-off jattool-minimal for testing machines * Changed jats: ids to use double-slash between suite part and test part * Added error message if test has not finished cleanly * Rewrote broken parts of test discovery and identification * Codebase maintenance