You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gno test command should have a -covermode flag, which allows to set -covermode count. (Note: -covermode atomic is not necessary in Gno, being single-threaded)
This works by "counting" the number of times the statements are covered, rather than simply detecting whether they are covered at least once.
The -covermode atomic results should be accessible through the cover profile.
The CI on examples should be set to use -covermode atomic.
I have a request regarding this issue, or possibly one of the two related issues.
Can we ensure that the system we set up will allow us to compute more information than just counting how many times a line was hit? I believe we also want to monitor metrics such as "gas consumed" per line and per iteration. Additionally, this will be a place where we can track "allocs" if we decide to differentiate between execution gas and storage gas.
Depends on #1121
Bounty Requirements
gno test
command should have a-covermode
flag, which allows to set-covermode count
. (Note:-covermode atomic
is not necessary in Gno, being single-threaded)-covermode atomic
results should be accessible through the cover profile.examples
should be set to use-covermode atomic
.Bounty Size: M; expected maximum reward: $2,000.
Find out more on the bounty program. If you participate with intention of receiving the bounty, you must agree to the Bounty Terms and Conditions.
More bounties | Contributing guidelines
The text was updated successfully, but these errors were encountered: