Having to refer all the way down assert self.contract.storage[index] == is a bit tiresome, and also we dont check all the things that shouldnt change. I propose we want ability to easily:
- declare what values should be:
- for consequentive array entries(also change by certain factor/addition)
- for values that are zero
- declare that a value has changed by a certain factor or addition.
- for balances, declare change-by-addition excepting fees
- track changes
- declaring things shouldnt (have) change(d)
- declaring nothing change(d) other than specified
- exceptions to the above
- track transactions
- how many of them
- any of their attributes, as (non)specific as desired.
- how it stopped, or the whole 'logic path'
With the latter i mean, now we check simulation.stopped, we could instead have .cll(heard name .hll floating around too?) files scan for comments besides those on stop, and make a list. Then you could check that entire flow.
jorisbontje mentioned testing libraries. (pytest, nosetest or unittest) To be honest i am not familiar about them, or how they fit in.
Having to refer all the way down
assert self.contract.storage[index] ==is a bit tiresome, and also we dont check all the things that shouldnt change. I propose we want ability to easily:With the latter i mean, now we check
simulation.stopped, we could instead have.cll(heard name.hllfloating around too?) files scan for comments besides those onstop, and make a list. Then you could check that entire flow.jorisbontje mentioned testing libraries. (
pytest,nosetestorunittest) To be honest i am not familiar about them, or how they fit in.