Test coverage

There are currently 58 implemented tests, but test coverage is patchy. I implemented code-coverage reporting, using the JaCoCo Gradle core plugin. I now have a benchmark for test coverage.

Cheating

When "test playing" the game it would save time if I could bypass the guess-work required to navigate to a particular sector or quadrant, without resorting to a scientific calculator. A "cheat" or "wizard" mode could allow access to this feature, with a configuration option to enable and disable access the cheat.

Logged as issue #20

Another slow test

The testGame() method is very slow, e.g. nearly two and a quarter seconds on an old laptop. I suspect it has the same cause as issue #18 i.e. Trek is a sub-class of LoggingBase.

09-MAR-2019 👈 Top of page 👉 11-MAR-2019

© 2020 Terry Ebdon.

Find me coding on GitHub, networking on LinkedIn, answering questions on Stack Exchange and hanging out on twitter.