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

Remove test suites #929

Open
morremeyer opened this issue Jan 3, 2024 · 2 comments
Open

Remove test suites #929

morremeyer opened this issue Jan 3, 2024 · 2 comments
Labels
development Things that support development of the software

Comments

@morremeyer
Copy link
Member

morremeyer commented Jan 3, 2024

With in-memory SQLite databases used for testing, we can remove the test suites since each in-memory database is distinct.

This adds two lines of code to each test that needs the database (calling the setup function and then deferring the teardown), but this is a better developer experience than the test suites currently since these are not well integrated into IDEs.

@morremeyer morremeyer added the development Things that support development of the software label Jan 3, 2024
@morremeyer
Copy link
Member Author

morremeyer commented Jan 13, 2024

When implementing this, check if we can use hooks to clean up more efficiently: https://medium.com/@jarifibrahim/using-gorm-hooks-to-clean-up-test-fixtures-in-golang-99b0fcb04354, probably in a combination with a TestMain function.

@morremeyer
Copy link
Member Author

There has been movement in fixing the VSCode Go Extension to also support testify Suites again, see golang/vscode-go#3128.

If that gets released, this issue is obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Things that support development of the software
Projects
None yet
Development

No branches or pull requests

1 participant