Test trails

[Mario5Gray]

Elaborate on testing in documentation. Discuss how testing works in each project, and what each module brings to the testing regiment.

Familiarize the reader with technologies used in testing such as :

• TestContainers

  • Test Containers is anywhere needed, but to remember this correctly try abstracting the workflow around
  • starting container lifecycle (waiting , timeout etc..) and setting dynamic properties

• Consul Tests

  • Dont test spring-cloud-discovery
  • Testing Consul KV stores is implemented

• Properties Tests

  • Old bootstrap.yml code is gone
  • Direct classpath yml files to a central location
  • specify yml to load on start using spring.config.location property

• Polymorphic Tests (and the anti-patterns we've already introduced)

  • Simple! Limit to 1 super.
  • E.G. TestContainersLifecycleTests, CassandraTestContainersLifecycleTests, Consul.... You get the idea
  • Nothing below that or else tests will become supper duper complicated and thats not good since
  • refactoring code also means refactoring tests (yikes)

• Apply CI/CD pipeline for tests

  • Just one step alone for project-root:'mvn test'
  • another step for mankind

[Mario5Gray]

Everything done even CI/CD (using TilT) only we need to synthesize a tilt coordination task for each project that needs it.