Add cheatcode test

[smiasojed]

How to reproduce:
cargo test --package forge --test it -- revive::cheats_individual --nocapture
failures:

    revive::cheats_individual::test_dump_state::case_1_evm
    revive::cheats_individual::test_expect_call::case_1_evm
    revive::cheats_individual::test_expect_create::case_1_evm
    revive::cheats_individual::test_expect_revert::case_1_evm
    revive::cheats_individual::test_get_raw_block_header::case_1_evm
    revive::cheats_individual::test_record::case_1_evm
    revive::cheats_individual::test_record_account_accesses::case_1_evm
    revive::cheats_individual::test_record_debug_trace::case_1_evm
    revive::cheats_individual::test_roll::case_1_evm
    revive::cheats_individual::test_set_blockhash::case_1_evm

[alexggh]

@smiasojed etch, prank, mock tests were already ported by me and passing here:

foundry-polkadot/crates/forge/tests/it/revive/mod.rs

Line 5 in b6b6f0c

pub mod cheat_mock_call;

[smiasojed]

yes I saw it, I will clean this up. But anyway original etch is failing - probably issue with EXTCODECOPY - but it should not affect our EVM path.

[alexggh]

yeah EXTCODECOPY compilation was the reason I modified. the test slightly.

[smiasojed]

I think we should not error out in this case, because it means that we do not have pvm code which is fine for evm path. @pkhry WDYT?

[pkhry]

error out

[smiasojed]

It means that if any project uses opcodes not supported in PVM, the EVM tests will fail. I’m not sure if this is the right approach.

[pkhry]

It means that if any project uses opcodes not supported in PVM, the EVM tests will fail. I’m not sure if this is the right approach.

then just disable pvm for now i guess

[smiasojed]

or if compilation for pvm fails just skip this bytecode in dualcompiledcontract - the user will not be able to switch to pvm in test

[pkhry]

for RecordAccountAcceses, partial, but makes stuff work - #443

[pkhry]

shouldn't this be */{}/{}.t.* to correctly grab tests by their filename?

[smiasojed]

yes there is a bug