Skip to content

feat: scaffold e2e testing harness, move devnet dump generation to a separate script - #421

Closed
m-kus wants to merge 1 commit into
02-04-feat_indexer_sync_code_and_spec_update_guidelines_and_todosfrom
02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script
Closed

m-kus wants to merge 1 commit into
02-04-feat_indexer_sync_code_and_spec_update_guidelines_and_todosfrom
02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script

Conversation

@m-kus

@m-kus m-kus commented Feb 5, 2026 •

Copy link
Copy Markdown

Update test fixture generation with dedicated e2e package

TL;DR

Adds a new e2e package with dedicated scripts for generating test fixtures, replacing the previous approach of using SDK tests with environment variables.

What changed?

  • Created a new e2e package with a dedicated script for generating test fixtures
  • Updated fixture generation instructions in READMEs to use the new approach
  • Added smoke tests in the e2e package to verify the indexer works correctly
  • Implemented helper classes for test environment setup and indexer client management
  • Removed the old environment variable-based fixture generation from the SDK

How to test?

cd e2e && npm run generate-dump

This will regenerate all fixtures for both discovery-core and discovery-service. Then run cargo test to verify the Rust tests still pass with the new fixtures.

Why make this change?

The previous approach relied on SDK tests with environment variables to generate fixtures, which was error-prone and difficult to maintain. The new dedicated e2e package provides a cleaner, more maintainable solution with explicit scripts for fixture generation. This also sets up infrastructure for proper end-to-end testing of the entire system, including the indexer.


This change is Reviewable

m-kus commented Feb 5, 2026 •

Copy link
Copy Markdown
Author

@m-kus
m-kus marked this pull request as ready for review February 5, 2026 14:20
@m-kus
m-kus force-pushed the 02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script branch from 6f9ca3b to 97bd0b2 Compare February 5, 2026 14:37
@m-kus
m-kus force-pushed the 02-04-feat_indexer_sync_code_and_spec_update_guidelines_and_todos branch from f40c228 to 090111f Compare February 5, 2026 21:23
@m-kus
m-kus force-pushed the 02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script branch from 97bd0b2 to 732c811 Compare February 5, 2026 21:23
@m-kus
m-kus force-pushed the 02-04-feat_indexer_sync_code_and_spec_update_guidelines_and_todos branch from 090111f to 871ff0b Compare February 5, 2026 21:29
@m-kus
m-kus force-pushed the 02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script branch from 732c811 to 4c8a839 Compare February 5, 2026 21:29
@m-kus
m-kus force-pushed the 02-05-feat_scaffold_e2e_testing_harness_move_devnet_dump_generation_to_a_separate_script branch from 4c8a839 to f5ad9ee Compare February 5, 2026 21:34
@m-kus
m-kus force-pushed the 02-04-feat_indexer_sync_code_and_spec_update_guidelines_and_todos branch from 871ff0b to 1d4d751 Compare February 5, 2026 21:34
@m-kus m-kus closed this Feb 9, 2026
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.

1 participant