This project provides some plugins for the PySys System Test Framework that will be useful if your application is written in Java(R). Features include:
- compiling Java test tools from your tests;
- easily starting Java processes, with convenient mechanisms to specify the classname/.jar, classpath and JVM arguments;
- executing JUnit test classes just like other PySys tests (providing a unified approach between your system and unit testing);
- generating Java code coverage reports.
If you are interested in creating your own PySys plugin for another language or toolset, this project also serves as a good example of how to structure, test, document and package it, including:
- creating a PySys test plugin to make help methods available to all your testcases;
- creating a PySys descriptor loader that dynamically creates PySys test descriptors based on the files; found under a directory (in this case, .java JUnit test classes), allowing seamless integration of JUnit testing alongside your other PySys tests;
- creating a PySys writer plugin to generate code coverage reports;
- using GitHub Actions to run PySys tests to check the plugins work correctly (with Python code coverage);
- building HTML documentation for the plugins (with cross-references to the main PySys documentation);
- generating a Python .whl package for installing them, and a GitHub Actions workflow for uploading to PyPi.
Feel free to fork this project and use as a starting point for your own plugins that add support for new languages/toolsets to PySys. To make it easy to reuse code from this plugin project it has a "Public Domain" license.
If this project inspires you to create new PySys plugins that may be useful for others in the PySys community, please consider whether you could make them available as an open-source project and on PyPi so that everyone can benefit.
For more information about the features of this plugin and how to install and use it, see the documentation: https://ben-spiller.github.io/pysysjava/
This repo uses a Maven POM to download the Java dependencies used for testing and for building the sample application. However Maven isn't used by the plugin itself so if you prefer to download the jars through some other mechanism that's fine.