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

Optimize tests #2573

Open
3 tasks
JanCizmar opened this issue Oct 11, 2024 · 1 comment
Open
3 tasks

Optimize tests #2573

JanCizmar opened this issue Oct 11, 2024 · 1 comment
Labels
cold It's good to know. But we don't want or cannot do it right now. So lets it in the future. stale

Comments

@JanCizmar
Copy link
Contributor

  • Prevent truncating db between each test
    • I have already started with this in this PR chore: Don't truncate database tables between tests #2572, please continue with rest of the tests
    • If it's not possible to simply make the data unique, please just add the @CleanDbBeforeMethod annotation and dont't waste much time with that
    • Run tests in profiler and search for scheduled operations running in separate thread and prevent this in tests and enable it only for tests where such behaviour is required
    • You can find these by searching for "@scheduled"
    • Join fast suites "data:test", "ee:test", "security:test" to single run, so we don't have to start it in multiple VMs as we do now.
@JanCizmar JanCizmar added the cold It's good to know. But we don't want or cannot do it right now. So lets it in the future. label Dec 5, 2024
Copy link
Contributor

github-actions bot commented Jan 5, 2025

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cold It's good to know. But we don't want or cannot do it right now. So lets it in the future. stale
Projects
None yet
Development

No branches or pull requests

2 participants