Beta test near-runner

[thisisjoshford]

Beta test near-runner and provide feedback

• [x] @mehtaphysical
• [x] @doriancrutcher
• [x] @BenKurrek

[BenKurrek]

Creating a feedback document

• Section 3 (boostrap) --> path.join(__dirname, '..', 'path', 'to', 'compiled.wasm') Is it possible to have path.join(__dirname, ‘insert path to compiled wasm’)

• Currently section 3 has describe('my contract' and section 4 also has describe('my contract' if the describes are doing different things (first is deploying the contract) and the second is writing tests, maybe you could call the first one describe('deploy contracts' and then the second describe('tests for contracts' or something like that

[thisisjoshford]

@mehtaphysical @doriancrutcher can you leave a feedback doc here for @chadoh and @willemneal ?

[doriancrutcher]

Here is my feedback document; contents:

I think the runner is pretty interesting!

I had a bit of trouble fully understanding how to set it up at first. So I set it up as a nodeJS file and ran it that way, even though the instructions made it seem like it was more for client side usage.

That being said once I got it running it seemed like I was able to successfully deploy my contract to my “local mini blockchain” and run my tests.

If running this as a node script was not the way to go about doing this I would be interested in learning more about the proper way to set this up.

[mehtaphysical]

feedback

[thisisjoshford]

@chadoh @willemneal here is some recorded feedback on near-runner :)

[willemneal]

@mehtaphysical I can't get access to the doc.

[chadoh]

Can people please edit their comments here and paste their notes right inline, rather than making me click links to external documents? 🙂