End to end tests

We discussed both on Discord and in #40 about adding end to end tests. These tests would work as follows (let me know if I missed any step):

• Create a new virtual environment
• Install nile
• Install cairo using nile install
• Initialize a new repository with nile init
• Compile the project
• Run tests
• Setup an account for the user (note: requires a private key)
• Deploy smart contract
• Use the account to interact with the smart contract
• Read value back from smart contract

This series of commands tests everything available in nile except nile node, which could be tested by running all steps that involve a network interaction twice (with local node and with test network).

Since StarkNet does not have transaction fees for now we can generate a new private key every time we run the tests and then let the account rot (we can’t destroy it anyway).

Any thoughts?

[fracek]

I think we have everything except we don’t test interactions between node and nile. I think that’s fine since we would be testing starknet-devnet more than nile itself.

[martriay]

I’m curious about the reason for having nile install to install cairo-lang and starknet-devnet, instead of including those in the installation requirements. The second option would avoid needing tests (that set up a virtual environment etc), but I’m sure there’s a design decision that I’m not aware of:)

The reason is that back in the day installing Cairo wasn’t as easy as pip install cairo-lang, so an utility for installing was useful – moreover with a new Cairo version every two weeks. I still believe there’s value in setting up a whole environment from scratch, although we have nile init for that.

Agree with everything else, although if we can avoid adding docker as a requirement I’d vote for it. Reasons being dependency minimization and that I already work on a docker environment.