Download JAR files tagged by test with all dependencies

Basic Java 8 archetype. Options: -testLibrary: [junit, testng, none]. DEFAULT: junit. Adds the requested test library to the POM deps. -compilerMode: [simple, test-only, retrolambda-main, retrolambda-all]. DEFAULT: simple. --simple: everything is compiled as Java 8. --test-only: set up test for Java 8, and main for Java 7. --retrolambda-main: main code is compiled as Java 8, and then converted to Java 7 via retrolambda. --retrolambda-all: all code is compiled as Java 8, and then converted to Java 7 via retrolambda. NOTE: Retrolambda support provided "as is" - if you have any problems, please file a ticket on the GitHub page!

The SigTest open source project is a collection of tools based on Oracle's commercial SigTest tools product. The SigTest tools can be used to compare APIs and to measure the test coverage of an API. Warning: this is an unofficial build of the open source SigTest tool made specifically for the Maven central repository by Alexey Gavrilov (mailto: [email protected]).

The Proton system tests execute against either the Java or the C implementations, based on the chosen profile. To execute, run either "mvn test -P proton-j" or "mvn test -P proton-jni". To reduce the set of Python tests run, set system property proton.pythontest.pattern, for example: mvn test -Dproton.pythontest.pattern='proton_tests.transport.TransportTest.*' The proton-jni profile looks for the JNI jar and native libraries under directory <basedir>/build/proton-c. To override this, run Maven like so: "mvn test -P proton-jni -Dproton-c-build-dir=/path/to/build/dir".

Java Validation Framework (not a JSR-303 implementation). This framework allows to modify (correct) test values; supports validation of localized values; allows to convert values into and from text representation; formats error messages, depending on the context; supports metadata, which allows to check any entity types (not only Java Beans or POJOs) and more. Also this framework has long list of predefined validation components.

Class implementing a HyperPipe classifier. For each category a HyperPipe is constructed that contains all points of that category (essentially records the attribute bounds observed for each category). Test instances are classified according to the category that "most contains the instance". Does not handle numeric class, or missing values in test cases. Extremely simple algorithm, but has the advantage of being extremely fast, and works quite well when you have "smegloads" of attributes.

Sometimes we sacrifice encapsulation just to let us access a method or field of an object from its unit tests. This framework uses reflection and dynamic proxies to access private portion of your objects, allowing you to keep them strongly encapsulated and still be able to test their internals using the provided accessors.

JExample is an extensions of JUnit that improves defect localizaton by changing the way you structure your tests. It introduces first-class dependencies. If test B depends on A, the return value of A can be used as B's fixture. And if A test fails, B and all other dependees of A are skipped and marked as white. We show in an empirical study that JExample improves performance and defect localization.

Contains the main Multiverse STM Implementation: the Alpha Engine. The Alpha engine supports readonly and update transactions. It also supports the retry/or else mechanism. This not the jar you want to have in your final distribution because it isn't instrumented (hence the name unborn). The jar you eventually want to have in your distribution is the multiverse-alpha jar. What this package does, is test the instrumentation for the Javaagent. The compiletime instrumentation is tested in the multiverse-alpha package (where all tests are copied and reexecuted but now with compiletime instrumentation).

This was the original artifact. It now adds dependencies for all of the other modules so that existing code will still continue to function until they change their dependencies. The modules that are not included in this are: niosax, maven, template test-framework and swing as they were not part of the original jar. To allow time for this migration, this module will remain in the project until 11.1 when it will be removed.

PatternTesting Check.CT (patterntesting-check-ct) is a quality framework that allows to automatically verify that Architecture/Design recommendations are implemented correctly in the code. It provides different checks of known anti patterns (like using System.out for logging) but provides also a test framework for better testing. The checks are done during compile time (this is the "CT" in Check.CT").