swagger-api / swagger-api/swagger-codegen

Spring Java Codegen test generation incorrect

Open
#9,646 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

Unit test code output for functions involving Java Map objects does not generate a valid stub since it tries to instantiate the "Map" interface instead of a concrete class (like HashMap)

Swagger-codegen version

3.0.10

Code output

(snippet of test)

    @Test
    public void queryTest() throws Exception {
        Map<String, Object> body = new Map();
        ResponseEntity<Message> responseEntity = api.query(body);
        assertEquals(HttpStatus.NOT_IMPLEMENTED, responseEntity.getStatusCode());
    }
Swagger declaration file content or url

Contributor guide

Open the 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.

Research direction

Reproduce the generated Spring Java test with the supplied OpenAPI YAML, then inspect the Spring Java code-generation templates or entry points responsible for request-body test stubs. Done means Map-based inputs generate a valid concrete implementation rather than instantiating the Map interface, and the generated test compiles.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.