test_start_containers.yml

parameters:
  - name: testMongo
    type: boolean

  - name: testRabbit
    type: boolean

  - name: testRedis
    type: boolean
    
  - name: testPostgres
    type: boolean

# If we need to run our tests against mongodb, rabbitmq, etc, what better way than to
# spin up an Actual service? This isn't technically kosher for unit tests, but for
# something designed specifically to interact with these services, it gives a greater
# level of confidence that the functions are working with the actual target service.

steps:

# MONGO DB
- ${{ if parameters.testMongo }}:
  - script: docker pull 'mongo:4.2'
    displayName: Downloading MongoDB Docker image

  - script: docker run -d --name mongotest -p 127.0.0.1:57017:27017/tcp mongo
    displayName: Start Mongo

# RABBIT MQ
- ${{ if parameters.testRabbit }}:
  - script: docker pull 'rabbitmq:3.8-management'
    displayName: Downloading RabbitMQ docker image

  - script: docker run -d --name rabbittest -p 127.0.0.1:57018:5672/tcp rabbitmq:3.8-management
    displayName: Start RabbitMQ

# REDIS
- ${{ if parameters.testRedis }}:
  - script: docker pull redis
    displayName: Downloading Redis Docker image

  - script: docker run -d --name redis-test -p 127.0.0.1:6359:6379/tcp redis
    displayName: Start Redis

# POSTGRES
- ${{ if parameters.testPostgres }}:
  - script: docker pull postgres
    displayName: Downloading Postgres Docker image

  - script: docker run -d -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres --name postgres-test -p 127.0.0.1:5432:5432/tcp postgres
    displayName: Start Postgres