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

Refactor test suite to use mock data instead of the database #81

Open
R055A opened this issue Mar 21, 2022 · 1 comment
Open

Refactor test suite to use mock data instead of the database #81

R055A opened this issue Mar 21, 2022 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@R055A
Copy link
Contributor

R055A commented Mar 21, 2022

Currently, much of the existing test suite is using a test database and is consistently deleting all data in the database before each test case. This can cause conflict between test cases executed in parallel sharing the same test database resources. This is why the CI workflow is sequentially executing automated testing.

To remove the requirement of a database from the test suite would allow parallel workflow testing, would optimise test performance time, and would resolve the chance of push and pull request event driven CI workflows failing because of conflict between workflows executed by separate events that could share the same resources, such as a commit push event starting a new workflow before another workflow from a prior push event to the same repository branch has completed.

To remove sequential CI testing following removing the requirement of a database for testing, remove occurences of
max-parallel: 1 from the .github/workflows/node.js.yml

@R055A R055A added the enhancement New feature or request label Mar 21, 2022
@R055A R055A added the bug Something isn't working label Mar 21, 2022
@j-chad
Copy link
Contributor

j-chad commented Mar 24, 2022

this will be partially fixed in #90 and will be finished in a later ticket. The preferred solution is to use an in-memory database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants