-
Notifications
You must be signed in to change notification settings - Fork 1
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
Set up integration tests #6
Conversation
tests/integration/corbado_test.go
Outdated
"github.com/stretchr/testify/require" | ||
) | ||
|
||
func initClient(t *testing.T) corbado.SDK { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about we name it sdk() and daisy chain it in the actual tests?
@@ -0,0 +1,28 @@ | |||
//go:build integration | |||
|
|||
package integration_test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
subdirectories per group/tag?
}) | ||
|
||
require.NoError(t, err) | ||
assert.NotEmpty(t, rsp.Data.EmailLinkID) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should discuss this in whatsapp: do we want to assert on every field (lots of work but will catch the most bugs) or do we skips this and make the asserts easy aka "no error and 'some' data". maybe check the others, i think stripe is doing the first
No description provided.