test: Introduce TestingFramework struct (#532)

## What ❔

Additional layer of abstraction between tests and `Chain`. This is an
intermediate step - in following PRs I will better separate concerns
between `Chain` and `TestingFramework`. Additionally this separation
will make RevmRunner integration easier and more effective.

Note that in this PR we'll change how testing works in general - by
default locally RISC-V simulation will be disabled, it will be enabled
in CI. This change makes testing setup a bit more friendly for AI
agents.

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- The `Why` has to be clear to non-Matter Labs entities running their
own ZK Chain -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Is this a breaking change?
- [ ] Yes
- [X] No

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [X] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [X] Documentation comments have been added / updated.
- [X] Code has been formatted.

Author: 0xVolosnikov

.github/workflows/bench.yml

@@ -5,6 +5,10 @@ on:
 
 permissions: read-all
 
+env:
+    ZKSYNC_RISC_V_RUN: true
+    CI: true
+
 # Cancel previous runs that might be caused by appbin update
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}

.github/workflows/ci.yml

@@ -8,6 +8,8 @@ permissions: read-all
 
 env:
     CARGO_INCREMENTAL: 0
+    ZKSYNC_RISC_V_RUN: true
+    CI: true
 
 # Cancel previous runs that might be caused by appbin update
 concurrency:
@@ -41,7 +43,7 @@ jobs:
             - name: Compile
               run: cargo test --release --no-run
             - name: Run rust tests
-              run: cargo test --release -j 3 -- --skip verify_default_binaries
+              run: cargo test --release -j 3
     crypto_test:
         name: crypto crate tests
         runs-on: [matterlabs-ci-runner]
@@ -101,7 +103,7 @@ jobs:
                   ./dump_bin.sh --type singleblock-batch
                   ./dump_bin.sh --type multiblock-batch
             - name: Run binary checker
-              run: cargo test -p binary_checker -- --nocapture
+              run: cargo test -p binary_checker -- --nocapture --ignored
 
     e2e_prove:
         name: e2e_prove

.github/workflows/evm_terster_proof_run.yml

@@ -7,6 +7,10 @@ on:
 
 permissions: read-all
 
+env:
+    ZKSYNC_RISC_V_RUN: true
+    CI: true
+
 jobs:
     evm_state_tests:
         name: EF EVM state tests with proof run

.github/workflows/fuzz.yml

@@ -7,6 +7,10 @@ on:
 
 permissions: read-all
 
+env:
+    ZKSYNC_RISC_V_RUN: true
+    CI: true
+
 jobs:
     build-fuzz-targets:
         name: Build fuzz targets

AGENTS.md

@@ -72,10 +72,22 @@ cd zksync_os && ./dump_bin.sh --type for-tests
 ### Testing Infrastructure
 
 #### Integration tests
-The project uses a custom testing rig located in `tests/rig/` with the main abstraction being the `Chain` struct for in-memory chain state testing. Tests are organized in `tests/instances/` and follow this pattern:
+The project uses a custom testing rig located in `tests/rig/` with the main abstraction being the `TestingFramework` struct. Tests are organized in `tests/instances/` and follow this pattern:
 1. Set up initial chain state (predeployed contracts, balances)
 2. Define transactions to execute
-3. Call `run_block` to execute (typically runs both forward and proof systems, unless configured otherwise)
+3. Call `execute_block` to execute (typically runs both forward and proof systems, unless configured otherwise)
+
+Avoid direct `Chain` usage in test instances unless a low-level path is explicitly needed.
+
+To run rig-based tests without detailed executions logs use:
+```bash
+cargo test -p <crate-name> --features rig/no_print
+```
+
+By default, local rig runs skip RISC-V simulation unless `ZKSYNC_RISC_V_RUN` or `CI` is set. To force proving-mode simulation locally use:
+```bash
+ZKSYNC_RISC_V_RUN=true cargo test -p <crate-name>
+```
 
 #### EVM tester
 The EVM tester is used to run the Ethereum execution spec tests to check the EVM compatibility of ZKsync OS.

tests/binary_checker/src/lib.rs

@@ -39,6 +39,7 @@ mod tests {
     }
 
     #[test]
+    #[ignore = "runs only on CI / explicit opt-in"]
     fn verify_default_binaries() {
         verify_binary("singleblock_batch.text");
         verify_binary("multiblock_batch.text")

tests/common/src/zksync_tx/mod.rs

@@ -17,6 +17,7 @@ pub mod service_tx;
 pub mod upgrade_tx;
 
 /// Wrapper over all tx envelope kinds we feed into ZKsync OS.
+#[derive(Clone)]
 pub enum ZKsyncTxEnvelope {
     /// Standard Ethereum typed envelope signed by the corresponding address.
     Ethereum(TxEnvelope, Address),
@@ -114,6 +115,7 @@ impl From<ZKsyncServiceTx> for ZKsyncTxEnvelope {
 }
 
 /// ZKsync OS specific transactions wrapper.
+#[derive(Clone)]
 pub enum ZKsyncSpecificTxEnvelope {
     L1(ZKsyncL1Tx),
     Upgrade(ZKsyncUpgradeTx),