cgewecke
cgewecke
@ferittuncer This isn't currently an option. Have never thought about displaying this mostly because the ETH price is so volatile...out of curiosity how would you find it useful?
Re-opening, there's been another request for this...
Hi @blueto01h Yes this is a good idea. It might be slightly complicated from a user standpoint because they'd have to specify the contract and the function signatures of the...
@M1kep Interesting! Great, that's good to know.
@elenadimitrova Thanks for raising this - adding it to the README as a shortcoming. To capture this data automatically I think we'd need to inspect each transaction trace for `CREATE`...
@lsenta Yes, that's a good idea. Actually, I looked through your repo and was wondering where the missing contract is. Even the trace tracking idea mentioned above would require the...
Ok excellent! Thanks for the solution @lsenta. Will leave this open for the time being because I think it's still an issue / confusing for anyone who is using a...
> I believe that the intention is to only run tests during a mutation that touch the line you're mutating. The new coverage client continuously updates an in-memory map of...
> I'm not opposed to extending Vertigo with a command that allows you to do fault localisation. Oh ok, that's great! I will tentatively add tests/line to the work scheduled...
@yxliang01 > You meant you plan to implement reporting coverage per unit test? I was thinking something more like: ``` $ solidity-coverage --outputTestsPerLine ``` which would produce an object like:...