Introduce a new JUnit test category that lets us mark certain tests as
not ready for execution. The test task in the individual project
can then be configured to not run tests marked as `NotReady`.
For the CI server builds, add a fullTest test task that simply runs
tests as normal, and link it into the check task so it runs on builds.
This is not perfect, as the class under test must still compile, so it
must have at least the correct signatures of all the methods tested.
Also, it may be worth finding a way to distribute the NotReady interface
that doesn't require checking it into every project.
With exercism/exercism.io@54e1df3, we can now gather exercises into a
subdirectory. By separating the language track files from the
configuration and management files, it is easier to read the project.
- move gradle config under "exercises" too as it would make a mess
otherwise.
Apply generics to the internals of Element to remove
needless casting.
Tighten Element scoping and move into Deque for succintness (sp).
Add the execise into the grade test suite.
The tests assume that the Deque class is implemented with generics.
The example implementation keeps track of a circular head Element.
Completes one task in https://github.com/exercism/xjava/issues/3.
build: Extract common config to top-level build.gradle
We can inject plugin, repositories and dependencies directly from
the top-level build.gradle.
This extracts a common version of junit for all projects (and
updates anagram to use assertj, the junit matchers did not work
with 4.12).
Fixes https://github.com/winterchord/xjava/commit/d09fb713d19abbcbdaaa979adb59aa7fc94532fd#commitcomment-14962172
The original PR (https://github.com/exercism/xjava/pull/69) that this issue
could have been fixed in was merged before I could fix this issue.
This implementation does not generate a test suite based on the json
meta the hello-world exercise.
See https://github.com/exercism/todo/issues/13
Fixes https://github.com/exercism/todo/issues/35