Skip to content
This repository has been archived by the owner on Mar 23, 2021. It is now read-only.

Ensure non-regression of cnd REST API #1221

Closed
D4nte opened this issue Aug 16, 2019 · 1 comment
Closed

Ensure non-regression of cnd REST API #1221

D4nte opened this issue Aug 16, 2019 · 1 comment
Labels
⚗️ spike A time-boxed investigation with the primary goal of gaining knowledge

Comments

@D4nte
Copy link
Contributor

D4nte commented Aug 16, 2019

As a developer, I want to ensure that updating to a new version of cnd will not break my application by surprise.

Task: Research how we can non-regression test our REST API and ensure that we do not break it when we say that we do not break it.

Note:

  • Look at API contracts
  • Think about how a developer could validate its API usage against a common document
@D4nte D4nte changed the title Ensure cnd client compatibility - API contracts Ensure non-regression of cnd REST API Aug 16, 2019
@D4nte D4nte added the ⚗️ spike A time-boxed investigation with the primary goal of gaining knowledge label Aug 16, 2019
@D4nte D4nte mentioned this issue Aug 16, 2019
Closed
17 tasks
@thomaseizinger
Copy link
Contributor

Inlined into #1122.

@thomaseizinger thomaseizinger mentioned this issue Aug 19, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
⚗️ spike A time-boxed investigation with the primary goal of gaining knowledge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@D4nte @thomaseizinger