We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I like the simplicity of this package and the fact that it stays close to the standard library.
However, is there any reason for not passing the testing object to the setup/teardown methods? E.g.:
type TestSuite interface { SetUpSuite(t *testing.T) TearDownSuite(t *testing.T) SetUp(t *testing.T) TearDown(t *testing.T) }
Otherwise a I don't see a way for a test setup to fail cleanly (think integration tests which for example try to connect to a database during setup).
Alternatively, or even additionally, the above methods could return an error, and gosuite.Run would fail the test if not nil.
Thanks
The text was updated successfully, but these errors were encountered:
I second to this, setup and teardown should be able to fail as well
Sorry, something went wrong.
No branches or pull requests
Hi,
I like the simplicity of this package and the fact that it stays close to the standard library.
However, is there any reason for not passing the testing object to the setup/teardown methods? E.g.:
Otherwise a I don't see a way for a test setup to fail cleanly (think integration tests which for example try to connect to a database during setup).
Alternatively, or even additionally, the above methods could return an error, and gosuite.Run would fail the test if not nil.
Thanks
The text was updated successfully, but these errors were encountered: