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

Organize tests - separate unit and integration tests #723

Open
vdusek opened this issue Nov 21, 2024 · 0 comments
Open

Organize tests - separate unit and integration tests #723

vdusek opened this issue Nov 21, 2024 · 0 comments
Labels
debt Code quality improvement or decrease of technical debt. t-tooling Issues with this label are in the ownership of the tooling team.

Comments

@vdusek
Copy link
Collaborator

vdusek commented Nov 21, 2024

  • Currently, all our tests are located in the tests/unit/ directory, but not all of them are unit tests.
  • Go through all the tests in the tests/unit/ directory and classify them between unit/ and integration/ tests.
  • In the future, we should also introduce end-to-end tests, which ideally should execute Crawlers and check their results (using both the MemoryStorageClient and the ApifyStorageClient).

Edit: or we can just have one directory for unit/integration tests and one for e2e.

@vdusek vdusek added t-tooling Issues with this label are in the ownership of the tooling team. debt Code quality improvement or decrease of technical debt. labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debt Code quality improvement or decrease of technical debt. t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

No branches or pull requests

1 participant