narwhal icon indicating copy to clipboard operation
narwhal copied to clipboard

Add some e2e tests

Open bmwill opened this issue 3 years ago • 2 comments

Today we have a number of unit tests but I don't believe we have any end-to-end tests that are run with cargo test and it would be beneficial to have some sort of a smoke test other than needing to run the benchmarks.

bmwill avatar Apr 21 '22 23:04 bmwill

Totally agree on this @bmwill . We do actually have an engineering goal on our road map around it (see. 1.3 End-to-end testing) so we are definitely planning to work on this and dedicate the appropriate time to come up with something solid.

akichidis avatar Apr 26 '22 10:04 akichidis

See also MystenLabs/sui#5194

huitseeker avatar May 31 '22 19:05 huitseeker

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Aug 11 '22 02:08 github-actions[bot]

This issue was closed because it has been stalled for 7 days with no activity.

github-actions[bot] avatar Aug 18 '22 02:08 github-actions[bot]

We have e2e tests in the form of cluster tests (.//test_utils/src/tests/cluster_tests.rsand callers thereof) + long-running e2e tests (see ignored tests)

huitseeker avatar Aug 18 '22 22:08 huitseeker