-
Notifications
You must be signed in to change notification settings - Fork 5
test: create scenarios for asset query #204
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
Conversation
| id: expect.any(String), | ||
| token: expect.objectContaining({ | ||
| address: ETHEREUM_USDC_ADDRESS, | ||
| }), |
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 we add the chain in this assertion?
| ); | ||
| }); | ||
|
|
||
| describe('When fetching the asset with a specific time window', () => { |
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.
It seems this test is adding little value for e2e spec perspective.
| describe('Querying Asset Price History on Aave V4', () => { | ||
| describe('Given an asset/token available on the protocol', () => { | ||
| describe('When fetching the asset price history', () => { | ||
| it('Then it should return the asset price history', 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.
This test seems to not add value.
No description provided.