Skip to content

starknet_os_flow_tests: expect initial fuzz test addresses#13042

Open
dorimedini-starkware wants to merge 1 commit into03-03-starknet_os_flow_tests_split_fuzz_test_manager_from_contextfrom
03-03-starknet_os_flow_tests_expect_initial_fuzz_test_addresses
Open

starknet_os_flow_tests: expect initial fuzz test addresses#13042
dorimedini-starkware wants to merge 1 commit into03-03-starknet_os_flow_tests_split_fuzz_test_manager_from_contextfrom
03-03-starknet_os_flow_tests_expect_initial_fuzz_test_addresses

Conversation

@dorimedini-starkware
Copy link
Collaborator

@dorimedini-starkware dorimedini-starkware commented Mar 5, 2026

Note

Low Risk
Test-only changes that hardcode/validate initial contract addresses; main risk is brittleness if deployment order/salts change, causing fuzz tests to fail unexpectedly.

Overview
Adds deterministic address expectations for the fuzz test orchestrator and initial Cairo0/Cairo1 contracts using expect_test, plus a new test_fuzz_deployment_expect to assert (and update) those addresses.

Refactors the fuzz harness to use the fixed addresses by centralizing deployment in init_deployment, removing the orchestrator address from FuzzTestContext, and updating deploy/address-calculation and orchestrator calls to reference the expected FUZZ_ADDRESS_* constants.

Written by Cursor Bugbot for commit d97aec5. This will update automatically on new commits. Configure here.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Collaborator Author

dorimedini-starkware commented Mar 5, 2026

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@dorimedini-starkware dorimedini-starkware force-pushed the 03-03-starknet_os_flow_tests_expect_initial_fuzz_test_addresses branch from 787adf3 to d97aec5 Compare March 6, 2026 11:56
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.

2 participants