Add tests for product-service and gateway-service

Open
  • Is something wrong?
#146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, java, mongodb, spring-boot
Domain
testing-qa

Research direction

Start in the product-service module, whose pom already declares Testcontainers MongoDB and JUnit Jupiter test dependencies but has no test classes, and use account-service's test classes as the pattern. Add a @WebMvcTest controller test and a Testcontainers-backed component test. For gateway-service, add a basic context-load or routing test. Done when both modules run their tests green with mvn test.

Written by the indexing model from the issue text.

Description

enhancement

Problem

product-service has Testcontainers (MongoDB, JUnit Jupiter) test dependencies but no test classes. gateway-service has no working tests.

Suggested solution

  • product-service: add a @WebMvcTest controller test and a Testcontainers-based component test, following account-service.
  • gateway-service: add a basic context-load / routing test.
Dominant language
Java
Stars
12
Forks
7
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piomin/sample-spring-cloud-testing

All issues in piomin/sample-spring-cloud-testing

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.