Api-Testing getting a mess with vagrant

Im doing API-testing (no web-API).
I feel that I have a complicated setup.

For Development:
We are using a vagrant-box (suse) for development that gets all its files via an ansible playbook. Included are instructions to clone some repositories from git (license keys, startscripts, and the tests themselves that are written in ruby and then startet with ctest).

  • Creating docker swarm using ansible
  • bundler: command not found: rails with docker-compose on a sample project
  • connect to container from a remote machine
  • Docker running inside vagrant + remote python debugging in Pycharm
  • Many docker volumes, each for different user (swarm mode)
  • docker start a container after stopping
  • For testing:
    For testing I use a centos-node (diffeent os) that is setup by a similar playbook. Then files that have to be fresh are injected via a jenkins pipeline script into that node.

    I get frustrated configuring the tests on both machines because of the different setup (different working directories and so on). Then Vagrant is also a little bit slow.
    We want to have the tests in Jekyll so that they run once a day.

    I heard of docker being good for testing.
    We are not in need of a GUI.

    Would it be a good idea to switch to docker?

  • Jenkins Docker Pipelining inside Docker
  • how to setup continuos deployment from docker-hub to AWS ECS?
  • How to keep docker containers running when they are installed with ansible
  • Namenode runs on InternalIP:8020 in cloudera docker and causes applications to fail
  • DOCKER How to update update Hosts file from dockerfile or right in container?
  • Empty response while making a GET http request to the localhost server using Go
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.