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

Add integration tests #72

Open
wants to merge 6 commits into
base: enterprise
Choose a base branch
from
Open

Add integration tests #72

wants to merge 6 commits into from

Conversation

EnriqueL8
Copy link

No description provided.

awrichar and others added 2 commits June 21, 2023 11:19
When guessing the reason for an insert conflict, the query needs to exactly match
the configured database indexes. That means that the "name" and "networkName"
queries need to both include "version" as well, otherwise we risk grabbing a
row that isn't actually a conflict.

Signed-off-by: Andrew Richardson <[email protected]>
@@ -44,7 +43,8 @@ func (suite *TokensTestSuite) BeforeTest(suiteName, testName string) {
}

func (suite *TokensTestSuite) AfterTest(suiteName, testName string) {
e2e.VerifyAllOperationsSucceeded(suite.T(), []*client.FireFlyClient{suite.testState.client1, suite.testState.client2}, suite.testState.startTime)
// Makes no sense if we expect failing operations - need to discuss as part of PR review
// e2e.VerifyAllOperationsSucceeded(suite.T(), []*client.FireFlyClient{suite.testState.client1, suite.testState.client2}, suite.testState.startTime)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nguyer want to discuss this with you if possible, as part of 7781f8a you introduced a new error code and the operation doesn't succeed

I'm not sure if it's the case that we should remove this from the test and not expect all operations to succeed or that the code creates an operation too early before validating conflicts?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate on why we would "expect" failing operations here? Up to this point, any case with a failing operation has actually been a bug, and I can't think of any cases at the moment where we would expect a failing operation.

// Cannot delete published pools
suite.testState.client1.DeleteTokenPool(suite.T(), poolID, 409)
}
// func (suite *TokensTestSuite) TestE2ENonFungibleTokensSync() {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this test removed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry was just commented out whilst I was figuring out with test was failing and debugging it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants