stellar / integration-tests Goto Github PK

Most of the elements of this integration test suite run inside containers, except the monitor and ngrok. This means that running these integration tests require installing applications and tools locally which makes it harder to run these locally.

We should make it really easy and predictable for anyone to quickly run these integration tests.

We can make it easier to run these tests if they are entirely contained within containers that use their own network to communicate with each other (in addition to also use ngrok internally).

A follow up to stellar/go#1542 that switched us from Dep to Go Modules.

This repository uses dep to manage dependencies in the stellar/go repo. That repo no longer uses dep as of stellar/go#1542 which was just merged, and the scripts and Dockerfile's in this repo need updating.

Currently, integration tests take over an hour to complete. @bartek mentioned that the speed is limited by ngrok tunnels. We can use max 2 tunnels at the same time so we can only have 2 simultaneous jobs.

Is the limitation tunnels or processes?

If we wanted to speed this up, we could

1. upgrade our ngrok service. It looks like for a few dollars a month we could get 8 or 12 tunnels, and 1 or 2 simultaneous ngrok processes.

2. try Serveo. It's an ngrok replacement which allows 3 simultaneous tunnels for free. The site also says

Host it yourself

This free version is intended for evaluative and personal use and allows no more than 3 total simultaneous tunnels per instance.

Email me at [email protected] if you're interested in licensing Serveo for business use or otherwise need more than 3 tunnels at a time.

The tests in this build run on TravisCI, but we've moved all other builds to CircleCI. We should move this also.