Regression Test Suite Runner Trigger

WHAT IT DOES

Regression Test Suite Runner Trigger is a developer tool that triggers the execution of a regression test suite on-chain. It reads the test suite configuration (contract addresses, test files, and test parameters), previous test run results, test status (pending/running/passed/failed), chain ID, account nonce, gas estimates for test execution, and previous trigger records. The tool then guides you through triggering the test suite execution, recording the test run start, updating the test status, and syncing the test status across chains.

HOW TO USE

Connect your wallet via the built-in connector. Select the network where the test runner contract is deployed. Enter the test suite configuration as a JSON object (including contract addresses, test files, and parameters), the test runner contract address, and the payment token address (use address(0) for native token). The tool will read on-chain data and display a preview including: test runner address, payment token, account nonce, test status, previous test run result, estimated gas, and the test configuration. Review all details carefully. Click "trigger test suite" to execute the test trigger. The tool will guide you through three steps: verifying the test configuration, triggering the test suite execution, and recording the test run start.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to interact with the test runner contract. It reads the account nonce using `provider.getTransactionCount(deployer)` and test status using `getTestStatus()` which returns pending/running/passed/failed. Previous test run results are read via `getLastTestResult()` which returns the outcome of the last run. Gas estimates are calculated using `estimateGas` on the test runner's `triggerTests()` method with EIP-1559 fee data from `feeData`. The trigger transaction calls `triggerTests(configHash)` on the test runner contract, which starts the test suite execution and emits a `TestSuiteStarted` event. The tool stores the test configuration hash on-chain and records the trigger time. All transactions are built with EIP-1559 fee data, and the tool uses `effectiveGasPrice` from receipts for accurate cost accounting. The tool also checks the user's balance against the estimated gas cost before initiating the trigger.

WHAT IT CANNOT SEE

This tool cannot guarantee that the test suite will pass or fail correctly—it only triggers the execution. It cannot detect if the test environment is properly configured (e.g., correct contract addresses). It cannot ensure that test results are reproducible across runs. It cannot validate that test coverage is complete. It cannot predict if tests will uncover regressions. It cannot detect if the contract state has changed during test execution. It cannot verify that test execution is properly isolated from other processes. It cannot ensure that test results are consistent across different runs or environments.

PLEASE NOTE

This tool is EVM-only and supports Ethereum, Polygon, BNB Chain, Arbitrum, Optimism, and Avalanche. The trigger transaction is signed by the connected wallet, and the user pays gas fees. Triggering a test suite does not guarantee that the tests will run immediately—execution depends on the test runner implementation. The tool does not store or transmit any test configuration data. Always verify the test configuration before triggering.