test environment in api versioning

Pragya Keshap answered on February 6, 2023 Popularity 5/10 Helpfulness 1/10

answer test environment in api versioning

test environment in api versioning

Comment

Contract testing is a powerful concept that allows very fast and robust test automation. However, we shouldn't forget that contract tests are still tests. Sometimes tests fail because of bugs in the code, but sometimes they fail due to expected changes in the code. There are times when we need to update an API so that it invalidates the contract that we have laid out in the specification file. In those cases, we need to update the API definition. However, what if there are people who are still relying on the functionality to work in the way that it used to?

One common way to deal with this problem is by versioning the API. In this section, you will learn about API versioning and when it makes sense to use it.

When you define API versions, you can pick which version of the API you are using when you call the endpoints and it will give back responses that match the specified version. But how do you set that up in Postman? Well, you can create a...

@RestController
@RequestMapping("/person")
public class PersonController {

    @Autowired
    PersonMapper mapper;
    @Autowired
    PersonRepository repository;

    @PostMapping({"/v1.0", "/v1.1"})
    public PersonOld add(@RequestBody PersonOld person) {
        return (PersonOld) repository.add(person);
    }

    @PostMapping("/v1.2")
    public PersonCurrent add(@RequestBody PersonCurrent person) {
        return mapper.map((PersonOld) repository.add(person));
    }

    @PutMapping("/v1.0")
    @Deprecated
    public PersonOld update(@RequestBody PersonOld person) {
        return (PersonOld) repository.update(person);
    }

    @PutMapping("/v1.1/{id}")
    public PersonOld update(@PathVariable("id") Long id, @RequestBody PersonOld person) {
        return (PersonOld) repository.update(person);
    }

    @PutMapping("/v1.2/{id}")
    public PersonCurrent update(@PathVariable("id") Long id, @RequestBody PersonCurrent person) {
        return mapper.map((PersonOld) repository.update(person));
    }

    @GetMapping({"/v1.0/{id}", "/v1.1/{id}"})
    public PersonOld findByIdOld(@PathVariable("id") Long id) {
        return (PersonOld) repository.findById(id);
    }

    @GetMapping("/v1.2/{id}")
    public PersonCurrent findById(@PathVariable("id") Long id) {
        return mapper.map((PersonOld) repository.findById(id));
    }

    @DeleteMapping({"/v1.0/{id}", "/v1.1/{id}", "/v1.2/{id}"})
    public void delete(@PathVariable("id") Long id) {
        repository.delete(id);
    }

}

https://www.techtarget.com/searchapparchitecture/tip/Get-started-with-API-versioning-and-URIs

Popularity 5/10 Helpfulness 1/10 Language java

Source: Grepper

Tags: environment java

Link to this answer
Share Copy Link

Contributed on Feb 06 2023

Pragya Keshap

0 Answers Avg Quality 2/10

test environment in api versioning

Contents

More Related Answers

test environment in api versioning

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.