-
Notifications
You must be signed in to change notification settings - Fork 47
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
added more cs tests #1418
added more cs tests #1418
Conversation
…rsx/mx-api-service into feat/chain-simulator-e2e
…rsx/mx-api-service into feat/chain-simulator-e2e
- Removed `beforeAll` hooks that called `ChainSimulatorUtils.waitForEpoch(2)` from multiple e2e test files: - This change simplifies the test setup and improves test execution time.
…seconds to ensure proper deployment of the PingPong smart contract.
- Implement tests for GET /tags, including validation of response structure, pagination, and search functionality. - Add tests for GET /tags/count to verify the count of tags. - Include tests for GET /tags/:tag to ensure correct tag details are returned. - Enhance overall test coverage for the tags feature in the chain simulator.
- Implement tests for GET /collections/:collection/nfts to validate NFT retrieval, pagination, and filtering by various parameters (search term, identifiers, tags, creator, etc.). - Add tests for GET /collections/:collection/nfts/count to verify NFT count based on different criteria.
- Moved the issuance of NFT collections to occur after funding the address and before issuing Meta-ESDT collections. - This change improves the logical flow of the test data preparation process.
…arison - Changed balance assertions from numeric comparison (expect(account.balance).toStrictEqual(1)) to string comparison (expect(account.balance).toStrictEqual("1")) in multiple test cases. - This ensures consistency in data type handling for balance values across the tests.
…seconds to allow for additional processing time during test data preparation.
… response validation, and enhance property checks
} | ||
}); | ||
|
||
it('should return transactions for a collection of type NFT with a specific hashes', async () => { |
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.
with a specific hashes -> with specific hashes
} | ||
}); | ||
|
||
it('should return transfers for a collection of type NFT with a specific hashes', async () => { |
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.
with specific hashes
@@ -1545,4 +1528,461 @@ describe('Accounts e2e tests with chain simulator', () => { | |||
expect(response.data).toStrictEqual(expectedCount); | |||
}); | |||
}); |
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.
I would split this into shorter files.. they are to big to even look at them
@@ -149,4 +130,1185 @@ describe('Collections e2e tests with chain simulator', () => { | |||
expect(response.data.collection).toBe(collection[0]); | |||
}); | |||
}); |
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.
I would split this into files based on the routes
Reasoning
Proposed Changes
How to test