Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: API Unit/Integration Testing #106

Open
SakuraIsayeki opened this issue Jul 30, 2022 · 0 comments
Open

Epic: API Unit/Integration Testing #106

SakuraIsayeki opened this issue Jul 30, 2022 · 0 comments
Labels
API Related to API development enhancement New feature or request help wanted Extra attention is needed

Comments

@SakuraIsayeki
Copy link
Owner

Context:

Developing a new feature doesn't always yield on first try. There can be unexpected bugs/errors, within said feature, or any related feature (regressions).

Problem:

Currently, we need to test manually, or expose ourselves to runtime errors, during production.
How can we detect those bugs before deployment ?

Objective:

We need to predict broken features, with tests.

We must check our features prior to a new update/release. This should be done automatically.

Targets:

  • Minimum code coverage of 80%, then raised to 90% at a later stage.
  • Manual review from stakeholders, per new implemented features.

Conjectures:

Unit & Integration testing answers this issue, by trading off time for stability, and reducing the amount of bugs found in production/live ops.
This also has the additive side effect of making code more reusable, and pushing the developer towards Test Driven Development, which aids with clear feature implementations.

@SakuraIsayeki SakuraIsayeki added enhancement New feature or request help wanted Extra attention is needed API Related to API development labels Jul 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Related to API development enhancement New feature or request help wanted Extra attention is needed
Projects
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant