Updates the testing infrastructure to use the latest relesae of junit and
leverages the new extension mechanism to create an easy to use testing
framework. Also adds additional test coverage for several plugins.
Removes the dependency on legacy script compilation and now relies on script
discovery. In addition, the Gradle build scripts were refactored and updated
to be compatible with Gradle 5.0 and make use of the new java-library
configurations.
This is a large change that significantly simplifies the plugin build system by
having the kotlinc handle everything related to script compilation. Since we
no longer use package name rewriting, the "packageName" option has been dropped
from the gradle script API and has been removed from existing plugins.
In addition to simplifying the build system, it should also significantly speed
up build times. Previously we ran 2 build processes for every plugin and
didn't have fully working incremental compilation for scripts compared to 1
build process with built-in incremental compilation.
There were also some random pieces of code that referenced kotlinc directly, so
those have either been removed or refactored out.
Adds custom coroutines specifically for use within Actions. This
implements all features of the previous system, however, does not rely
on a separate executor to wake up continuations.
Note: since Actions are still ran by an executor and a small chance of
overlap exists the ActionCoroutine implementation uses atomic counters
and references.
Adds asynchronous implementations of the Action and DistancedAction
classes, allowing plugins to make use of suspendable functions in Kotlin
instead of creating mini state machines to keep track of state.
The asynchronicity works by creating coroutine backed Channels for each
asynchronous action and having them listen on "pulse" events from the
action scheduler. The action can then suspend execution until a pulse is
received or until some expensive operation has completed (i.e.,
pathfinding).
If an asynchronous action is still busy when a pulse arrives then the
number of missed pulses will be accumulated and sent to the action at
the next possible time.
The training dummy plugin has been updated to use asycnrhonous actions
as an example.
Refactors the test helpers to use receiver functions so multiple players
can exist in the world per test case. The AddFriendsTest is an example
of where this is needed.
Additionally, Hamcrest has been replaced with AssertJ for fluent
assertions.
Adds a basic testing framework suitable for plugins that start simple
Actions for players, which can be expanded on in the future. The
banking and training dummy tests have been updated to use this framework
and serve as samples.
david.indova@gmail.com