Decide on Unit Tests

[Monstarrrr]

Which Unit Testing Solution to use on the Front-end ?

• Impact: 🟡 Medium

• Status: 🔒 Decided

• Deciders & Confidence:

  • @purple-void (3.5 / 5️)
  • @seporterfield (3 / 5️)
  • @Monstarrrr (4 / 5️)

• Technical Story:

  • Write tests. Not too many. Mostly integration. - (kentcdodds.com)
  • Comparing Next.js Testing Tools and Strategies - (logrocket.com)

• Last updated: 09-06-2024

Context

Important decision because once chosen we won't be able to switch unless we rewrite a lot of code, presumably.

Decision Drivers

• Ease of use
• Scalability
• Performance

Considered Options

Jest

---

Jest is the default testing framework for NextJS

Ease of use:

• :green_circle: Easy to setup

Vitest

---

Vitest is a newer testing framework using vite

Ease of use:

• :orange_circle: Requires more setup than Jest

Performance

• :green_circle: Faster than Jest

None

---

No unit tests

Ease of use:

• :green_circle: No use needed

Scalability:

• :green_circle: Unit tests in React aren't good ROI.

• :green_circle: Won't use unit tests unless we have specific complex functions to test, which we don't have (yet).

• :orange_circle: Unit tests could facilitate refactoring and maintainability in the long run

Decision Outcome

Chosen option: "None (until a complex pure function is added)"
Reason: It may be too time consuming to setup unit tests for the MVP if we don't have complex pure functions we need to test.

Positive Consequences

• Faster MVP release

Negative Consequences

[Monstarrrr]

Need your confidence levels then close 😃

[purple-void]

Seems like unit testing is nice for confirmation and to make the code possibility more understandable, but we are fine without it "until a complex pure function is added"