Cucumber API & Async Test Suite -- 3
Budget: $10 – $30 USD
Our micro-services platform is written in Java, packaged with Maven, runs on Embedded Tomcat in Docker containers, and communicates through embedded Kafka (including embedded Kafka for local runs - camel routes) while persisting data in Cassandra. I already have the services up and running inside Kubernetes but have challenges running the application server as of now ; what I’m missing is a clean, maintainable set of functional tests.
Here is what I need from you:
• Write behaviour-driven Cucumber scenarios that cover the public REST APIs and the internal asynchronous Kafka flows.
• Implement the step definitions in Java or Kotlin, wiring them to the existing Maven build so they execute automatically in CI.
• Spin up any required dependencies (embedded Kafka, Cassandra test keyspace, mock upstream services) programmatically or via lightweight test containers so the suite remains fully self-contained.
• Make sure the tests can be triggered locally with a single Maven command as well as inside the Kubernetes pipeline.
Acceptance criteria
– Scenarios written in plain Gherkin, clearly describing API and async behaviours.
– Green test run from `mvn clean verify` on a fresh checkout without manual setup.
– Detailed README explaining how to execute the suite locally and how to extend it with new scenarios.
If this sounds like your daily bread, let’s talk and get these tests in place.
Here is what I need from you:
• Write behaviour-driven Cucumber scenarios that cover the public REST APIs and the internal asynchronous Kafka flows.
• Implement the step definitions in Java or Kotlin, wiring them to the existing Maven build so they execute automatically in CI.
• Spin up any required dependencies (embedded Kafka, Cassandra test keyspace, mock upstream services) programmatically or via lightweight test containers so the suite remains fully self-contained.
• Make sure the tests can be triggered locally with a single Maven command as well as inside the Kubernetes pipeline.
Acceptance criteria
– Scenarios written in plain Gherkin, clearly describing API and async behaviours.
– Green test run from `mvn clean verify` on a fresh checkout without manual setup.
– Detailed README explaining how to execute the suite locally and how to extend it with new scenarios.
If this sounds like your daily bread, let’s talk and get these tests in place.