Setup testing infrastructure for Common #2371

Closed
opened 2026-04-05 16:59:56 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @nawazdhandala on 4/20/2022

  • We have an directory "Common" where most of the common code across services lives.
  • There are no tests written for it.
  • To begin with, we need to set up testing infrastructure on common, which basically means we need to set up https://jestjs.io/ for this project.
  • Create a directory called "Tests" inside of "Common"
  • Set up jest https://jestjs.io/ testing framework for this project.
  • To begin with write tests for Common/Utils/UUID.ts
  • Make sure tests run when you run npm run test inside of Common
  • Set up GitHub Actions job for it and make sure they run on all branches except hotfix-*, release and staging-release. You can copy the workflow file from here: .github/skipped-workflows/test-saas.yaml
  • This PR should have that test job passing.
*Originally created by @nawazdhandala on 4/20/2022* - We have an directory "Common" where most of the common code across services lives. - There are no tests written for it. - To begin with, we need to set up testing infrastructure on common, which basically means we need to set up https://jestjs.io/ for this project. - Create a directory called "Tests" inside of "Common" - Set up jest https://jestjs.io/ testing framework for this project. - To begin with write tests for `Common/Utils/UUID.ts` - Make sure tests run when you run npm run test inside of Common - Set up GitHub Actions job for it and make sure they run on all branches except hotfix-*, release and staging-release. You can copy the workflow file from here: .github/skipped-workflows/test-saas.yaml - This PR should have that test job passing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#2371