Rappie
Rappie
+1 It is also cleaner in the UI to be able to remove unwanted/useless fuzz tests. At the moment I work around this by making variables internal as much as...
For me both "Failed" and "Not Covered" would compel me to look deeper into a property, and "Passed" would not. I would prefer: - If an assertion fails: Failed -...
+1 This would be really convenient to add if it's not too much work :slightly_smiling_face: However, you can exit out of Echidna and easily copy/paste it from the results that...
Output of `slither . --print echidna` ``` INFO:Printers:{ "payable": { "WithFallback": [ "()" ] }, "timestamp": {}, "block_number": {}, "msg_sender": {}, "msg_gas": {}, "assert": {}, "constant_functions": { "A": [ "a()"...
Yes. Just updated to the latest `master`. It will take some time to test this, if I encounter something i will share.
I've tested it with the repo in this issue. All issues remain, but the general speed is a bit higher.
Does `deployBytecode` support overwriting code on onchain addresses?
``` [2023-04-03 15:44:53.97] Compiling .... Done! (67.398573363s) Analyzing contract: .../echidna/Echidna.sol:Echidna [2023-04-03 15:46:01.60] Running slither on .... Done! (3.263365893s) Loaded total of 0 transactions from echidna-corpus/reproducers Loaded total of 0 transactions...
As requested, I tested this with `medusa`. It seems to be much faster: ``` fuzz: elapsed: 27s, call: 133944 (4465/sec), seq/s: 44, resets/s: 0, cov: 47 ```
Multiple (the default settings)