explicitly setup test scenario for test_query_default_page_limit

MystenLabs / sui

Sui, a next-generation smart contract platform with high throughput, low latency, and an asset-oriented programming model powered by the Move programming language

Apache License 2.0

5.84k stars 11.06k forks source link

Description

Unblock https://github.com/MystenLabs/sui/pull/18277 by explicitly setting up the correct test scenario for the test_query_default_page_limit test.

I think we can follow this up with

instead of using the same db url, follow sui-graphql-e2e-tests pattern and generate unique db urls for each test
this is so that we can run tests in parallel instead of sequentially (which is the case today due to the serial)
we can leverage ExecutorCluster.cleanup_resources to cleanup each test

Test plan

How did you test the new or updated feature?

Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:

MystenLabs / sui