Made with by giki

OLD-Possible-Layers

Contributed by kcooney

Here are some ideas on possible layers that we could build. Each of these layers could be an area of independent development.

Note that the features listed are not a definitive list; they are primarily there to help define what functionality could go in which layer.

Model

The model layer provides classes to represent a collection of tests.

This layer should be very generic, and could possibly represent not only JUnit3 and JUnit4 style tests, but Lambda-based tests and possibly tests from other test frameworks (like Fit and TestNG).

We may want to use build tools (Gradle, thenMaven) and IDEs for inspiration, since these systems often support more than one type of test.

Dependencies

None

Required Functionality

Possible Functionality

Challenges

Discovery

The discovery layer has functionality for finding tests.

Dependencies

Notification

The notification layer allows code to view the progress of running tests on a model.

Dependencies

Required Functionality

Notifications for - test run started/ending - leaf node started/ended - parent node started/ended - test skipped - test interrupted

Caller must be able to the Notification layer plus the Model layer to determine

Possible Functionality

Challenges

Test Engines

A test engine handles running a particular type of test (JUnit3, JUnit4, JUnit Lambda). It produces a portion of the Model, and provides an API for running tests.

Some of the functionality described in the Model layer might belong here instead, including sorting and filtering.

Dependencies

Challenges

Ideas