Hey, oftentimes I see myself having to run two types of tests in travis-ci: unitary and integration tests. For the first category, that usually means running some plain Golang code that interacts with no other services (e.g, it uses a mocked database or it mocks HTTP requests). In the other scenario, spawning Docker containers which end up creating a database that is used in the test - requiring docker to be present, thus, VM-based builds. Using the matrix property we can tailor our build mat...
