A collection of JUnit rules for testing code which uses java.lang.System.
Java
stefanbirkner Check methods of SecurityManager are overridden
NoExitSecurityManager is supposed to override all public methods of
SecurityManager. Currently for each new Java version I have to check
manually that this condition is satisfied. The new tests allows me to
check it automatically by running the tests with the respective JDK.
Latest commit 0d44f84 Jun 8, 2018

README.md

System Rules

Build Status Linux Build Status Windows

System Rules is a collection of JUnit rules for testing code which uses java.lang.System.

Installation

System Rules is available from Maven Central.

<dependency>
  <groupId>com.github.stefanbirkner</groupId>
  <artifactId>system-rules</artifactId>
  <version>1.18.0</version>
</dependency>

Please don't forget to add the scope test if you're using System Rules for tests only.

Usage

System Rules' documentation is stored in the gh-pages branch and is available online at http://stefanbirkner.github.io/system-rules/index.html

Contributing

You have three options if you have a feature request, found a bug or simply have a question about System Rules.

Development Guide

System Rules is build with Maven. If you want to contribute code than

  • Please write a test for your change.
  • Ensure that you didn't break the build by running mvnw test.
  • Fork the repo and create a pull request. (See Understanding the GitHub Flow)

The basic coding style is described in the EditorConfig file .editorconfig.

System Rules supports Travis CI (Linux) and AppVeyor (Windows) for continuous integration. Your pull request will be automatically build by both CI servers.

Release Guide

  • Select a new version according to the Semantic Versioning 2.0.0 Standard.
  • Set the new version in pom.xml and in the Installation section of this readme.
  • Commit the modified pom.xml and README.md.
  • Run mvnw clean deploy with JDK 6 or 7.
  • Add a tag for the release: git tag system-rules-X.X.X