blockifier_test_utils: add functionality to test contract for test_os_logic

[dorimedini-starkware]

No description provided.

[reviewable-StarkWare]

This change is 

[dorimedini-starkware]

• starknet_os_flow_tests: migrate test_v1_bound_accounts_cairo1 #9496 : 2 dependent PRs (#9501 , #9514 )
• starknet_os_flow_tests: add V1-bound cairo1 account for flow tests #9495
• starknet_api: fix compiler->SNAPI contract class ABI string conversion for tests #9494
• starknet_os_flow_tests: migrate test_v1_bound_accounts_cairo0 #9493
• starknet_os_flow_tests: split get_class_info_of_cairo0_contract into function #9492
• starknet_os_flow_tests: more informative execution failure #9491
• starknet_os_flow_tests: add V1-bound cairo0 account for flow tests #9490
• starknet_os_flow_tests: localize expected storage updates in test_os_logic #9485
• starknet_os_flow_tests: migrate test_os_logic and some small refactors #9484
• blockifier_test_utils: add functionality to test contract for test_os_logic #9483 👈 (View in Graphite)
• blockifier_test_utils: add test_contract2 cairo0 contract #9482
• blockifier_test_utils: add delegate_proxy cairo0 contract #9481
• starknet_os_flow_tests: add control for expected reverting txs #9480
• starknet_os_flow_tests: migrate test_reverted_l1_handler_tx #9474
• starknet_os_flow_tests: reduce boilerplate with add_funded_account_invoke #9563
• starknet_os_flow_tests: move nonce manager into test manager #9562
• starknet_os_flow_tests: migrate test_reverted_invoke_tx #9473
• starknet_os_flow_tests: reduce boilerplate with perform_default_validations #9472
• main

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

[github-actions]

Artifacts upload workflows:

• Started at 2025-10-01T08:51:50Z
• Started at 2025-10-05T07:45:07Z
• Started at 2025-10-05T09:37:48Z
• Started at 2025-10-06T16:50:48Z
• Started at 2025-10-09T09:33:27Z
• Started at 2025-10-09T09:46:40Z
• Started at 2025-10-09T11:10:16Z
• Started at 2025-10-14T10:21:27Z
• Started at 2025-10-15T11:16:05Z
• Started at 2025-10-15T11:53:03Z
• Started at 2025-10-19T07:04:58Z
• Started at 2025-10-19T18:42:20Z
• Started at 2025-10-22T08:58:10Z
• Started at 2025-10-22T10:22:28Z
• Started at 2025-10-22T10:22:40Z
• Started at 2025-10-22T15:01:48Z

[AvivYossef-starkware]

Why not adding every util in the PR which you need to use it?

@AvivYossef-starkware reviewed 10 of 10 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @meship-starkware and @Yoni-Starkware)

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 41 at r1 (raw file):

    func set_value(address: felt, value: felt) {
    }
}

I done see it in py test contracrt.
Consider create a new file test_contract_interface.cairo like we have in python

Code quote:

@contract_interface
namespace TestContract {
    func set_value(address: felt, value: felt) {
    }
}

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 74 at r1 (raw file):

    assert new_value = value + 1;
    return ();
}

I know that its coppied from pyhton but consider giving better name to the function

Code quote:

@external
func entry_point{syscall_ptr: felt*, pedersen_ptr: HashBuiltin*}() {
    const address = 15;

    let (value) = storage_read(address=address);
    storage_write(address=address, value=value + 1);
    let (new_value) = storage_read(address=address);

    assert new_value = value + 1;
    return ();
}

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 115 at r1 (raw file):

) {
    let (diffs: felt*) = alloc();
    assert (diffs[0], diffs[1]) = (amount, 0);

does diffs represent the amount of deposit for 2 different tokens?
why we update the balance index is according the l1_address?

Code quote:

assert (diffs[0], diffs[1]) = (amount, 0);

[Yoni-Starkware]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @AvivYossef-starkware and @meship-starkware)

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 116 at r1 (raw file):

    let (diffs: felt*) = alloc();
    assert (diffs[0], diffs[1]) = (amount, 0);
    advance_counter(index=from_address, diff_0=amount, diff_1=0);

Suggestion:

    advance_counter(index=from_address, diff_0=amount, diff_1=0);

[dorimedini-starkware]

tried to do that for most utils, but adding things to contracts makes the PR large sometimes + involves fixing existing tests

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @AvivYossef-starkware, @meship-starkware, and @Yoni-Starkware)

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 41 at r1 (raw file):

Previously, AvivYossef-starkware wrote…

I done see it in py test contracrt.
Consider create a new file test_contract_interface.cairo like we have in python

the issue is that in the blockifier we compile each contract as a standalone file; we cannot compile several modules into one JSON

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 115 at r1 (raw file):

Previously, AvivYossef-starkware wrote…

does diffs represent the amount of deposit for 2 different tokens?
why we update the balance index is according the l1_address?

removed the diffs, it wasn't needed

---

crates/blockifier_test_utils/resources/feature_contracts/cairo0/test_contract.cairo line 116 at r1 (raw file):

    let (diffs: felt*) = alloc();
    assert (diffs[0], diffs[1]) = (amount, 0);
    advance_counter(index=from_address, diff_0=amount, diff_1=0);

Done.

[github-actions]

Benchmark movements: No major performance changes detected.

[AvivYossef-starkware]

@AvivYossef-starkware reviewed 10 of 10 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @meship-starkware and @Yoni-Starkware)

[Yoni-Starkware]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @meship-starkware)

[dorimedini-starkware]

@dorimedini-starkware reviewed 10 of 10 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @meship-starkware)