Automatic testing, style checking and deployment about avalanche HOT 7 CLOSED

I'm already working on the doc (should be ready in few days), and no problem about defining a complete travis ci setup that tests if the code is "executable" at every new push to master and search for errors in every pull request.

Defining a complete testing strategy is quite a large task, since before automatizing the testing we have to write the tests for every basic functionalities! IMO we should open some issues with the aim of writing unit tests for every module before starting to automatize testing.

from avalanche.

Doc deployment and automatic testing (syntax errors and unit test) done.
If you agree I'd rename this issue "Automatic testing, style checking and deployment". First part done, second and third in development :)

from avalanche.

Yes, let's wait for @ggraffieti PR on this!

from avalanche.

Yes, this issue is more related to CI test infrastructure then the tests themself!

from avalanche.

ok!

from avalanche.

In my opinion this issue could be closed, since we opened another issue about the release of avalanche and the packetization of the application.
All the other points are solved.

from avalanche.

ok, can you open another issue for the "multiple checks" problem with trevis ci or to move to circle ci?

from avalanche.