In an effort to make more comprehensive testing on Travis, new types of tests will be created called integration tests. These tests will basically run docker containers and spin up a producer and maybe a few clients, interact in some meaningful way, and then make assertions based on some activity. An example would be spinning up a container with a producer and checking to make sure it does an airdrop correctly. These types of tests deal with systemic behavior after a potential code change has been made, as opposed to a unit test which simply tests one particular feature to make sure it's working.
For the first issue dealing with this, create a aurum docker package in internal that has a library file and a test file just like every other package. Naming is up to you.
As a first test simply copy the code from the container run example here and put it in a test function. If it runs without problems, then it is complete.
HarryL5004
commented
5 years ago
In an effort to make more comprehensive testing on Travis, new types of tests will be created called integration tests. These tests will basically run docker containers and spin up a producer and maybe a few clients, interact in some meaningful way, and then make assertions based on some activity. An example would be spinning up a container with a producer and checking to make sure it does an airdrop correctly. These types of tests deal with systemic behavior after a potential code change has been made, as opposed to a unit test which simply tests one particular feature to make sure it's working.
For the first issue dealing with this, create a aurum docker package in internal that has a library file and a test file just like every other package. Naming is up to you.
As a first test simply copy the code from the container run example here and put it in a test function. If it runs without problems, then it is complete.