Additional Color: I'm confident in the initial implementation since we're bringing our experience up to par with competitors, but I would like to know more from users on where it could go, in addition to what testing needs are unique to NEAR. I marked this is important rather than critical since there's not future work blocked at this moment, but it will be needed research going forward.
Who needs to be involved?
@mattlockyer and/or @mehtaphysical
@DiscRiskandBisque
Tasks to complete (can return to [x] these)
[ ] Gather more information on existing pain points around
[ ] testing NEAR contracts
[ ] NEAR's local development experience
What is the scope of this? (range: x-small is 1 hour, x-large is over a month of work)
[ ] x-small
[ ] small
[x] medium
[ ] large
[ ] x-large
What priority is this? (remove what doesn't apply)
[ ] P0 (EMERGENCY: drop everything to put out the fire)
[ ] P1 (Critical: docs, bugs, or features that block work or dev/app success)
[x] P2 (Important: known docs, feature requests, or known bugs)
[ ] P3 (Nice-to-have: docs or features that improve a flow)
What is this for?
near test
command tonear-cli
near-sdk-sim
in favor of a local development specific near node (as yet unnamed, internally callednear-Ganache
)Who needs to be involved?
Tasks to complete (can return to [x] these)
What is the scope of this? (range: x-small is 1 hour, x-large is over a month of work)
What priority is this? (remove what doesn't apply)