As a developer I can generate tests for my smart contract project once it's instantiated

[ibm-blockchain]

As a developer I can generate tests for my smart contract project once it's instantiated

[heatherlp]

So the generated test file will have some requires at the top for modules we need (i.e. fabric-network), meaning it needs a node_modules somewhere to grab them from.

After speaking to Simon and Ed, I think we should split this item into two:

1. the user developed the instantiated smart contract, and it's open in their workspace. The generated test file can live somewhere useful in the smart contract project and make use of the node_modules there. This will be delivered here.

2. they didn't develop it and they'd like to test it. Selecting "create smart contract tests" generates a test project (or similar) with it's own package.json etc for the modules the test file needs. This will be delivered under #214

We're not addressing usecase 1a (the developer developed the smart contract in vscode, but doesn't have that project open in their workspace) because we can't know where that project now lives.

[heatherlp]

This needs the following before it can be closed:

#260, #229, #261 , #262

[heatherlp]

Under merge of #313, users can now generate javascript test file for an instantiated smart contract, so closing