crytic / crytic/fuzz-utils

[Bug-Candidate]: If `deployContracts` is used, the generated test probably won't work

Open
#48 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Solidity
Stars
115
Forks
6
PR merge metrics
No merged PRs in 30d

Description

### Describe the issue:

Echidna allows contracts to be deployed to specific addresses using the `deployContracts` configuration option. However, when the tests are generated, only the harness is constructed and the other contracts are not deployed.

Not sure if this is an easy fix, just leaving it here for reference.

### Code example to reproduce the issue:

Not an exact reproducer, but a general idea.

In echidna config file:
```
deployContracts: [["0x12345", "ExampleContract"]]
```

In the echidna test contract:
```
constructor() {
ExampleContract ec = ExampleContract(0x12345);
uint256 value1 = ec.doSomething();
assert(value1 == 123);
}
```

### Version:

0.2.0

### Relevant log output:

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.