Francisco Giordano

@fulldecent Keeping this discussions URL was discussed and agreed with editors in this PR. There is no Ethereum Magicians thread, and the GitHub issue that hosts the discussion has had...

So is it okay if I remove the reference implementation and tests? Are all editors on board with that? @Pandapip1 @SamWilsn I assume this will require another author approval?

Removed reference implementation and tests. GitHub doesn't allow me to request reviews from multiple people.

@vicnaum No, but in that case I don't see what benefit there would be to using Test Environment! The main feature is that it will spin up Ganache for you...

What would be the scope of this? We clearly would allow choosing ethers.js contract abstractions, by specifying `contracts: 'ether'` in the config. Additionally, I suppose we would export a preconfigured...

Automatic awaiting of promises is a bad idea IMO. We can suggest use with `--experimental-repl-await` to be able to use await in the REPL. `truffle console` will still have more...

An idea. The problem is that the first transaction sent in the first test will wait until the node has spun up. We can work around this by allowing the...

It's not only about it being instant, it's about the accounts being available in the top level context, without having to do dirty tricks with `let accounts;` and assigning it...

My proposal is basically a workaround though. It would be nicer to do something more automatic, if we can figure it out.

Thank you for reporting @zgorizzo69. I'd be very surprised if this error was caused by Test Environment. Can you share what makes you think that it could be this library?