corda/experimental
Ross Nicoll 232db9a1fd Move test utilities into their own package
This moves a lot of the test support code into its own package which is only imported for tests,
so it's not shipped as a part of core Corda. The node currently depends on this support code to
compile, although future work could try to separate this out. This change highlights that parts
of production code is dependent on test elements (i.e. dummy keys), and makes it harder for
such accidental crosses to occur later.

An integration test category is also added as part of this work, to contribute towards COR-345.
2016-08-31 15:40:54 +01:00
..
src Move test utilities into their own package 2016-08-31 15:40:54 +01:00
build.gradle Move test utilities into their own package 2016-08-31 15:40:54 +01:00
README.md Add an experimental module. 2016-06-22 18:00:36 +02:00

Experimental module

The purpose of this module is to hold contracts/cordapps that aren't yet ready for code review, but which still want to be refactored and kept compiling as the underlying platform changes. Code placed into experimental must eventually either be moved into the main modules and go through code review, or deleted.

Code placed here can be committed to directly onto master at any time as long as it doesn't break the build (no compile failures or unit test failures). Any commits here that break the build will simply be rolled back.