Testing
Testing can be performed either locally (on your workstation) using docker images or on the hosted test server.
The test server is available at https://test.mymedlookup.org
Testing the application on your workstation involves pulling the application images and running them. The production application runs 2 web containers load balanced by nginx server, you can either run a simple configuration with one web server and database server or simulate the production environment with 1 nginx server connected to 2 web servers. The webservers are connected to the database server.
Jump to
Pull docker images
You can test the application locally on your box by pulling down docker images. A docker image build is triggered when changes are pushed to the github repository. Docker images are available for following branches
The following images are publicly available on docker hub API Prototype Images
Images built from develop branch
Images built from dev-integration branch
Images built from test branch
Images built from master branch
You can install any of the above images on your workstation to test the application. Please ensure you have docker installed on your workstation. You can follow the instructions here for installing boot2docker on mac and here for installing boot2docker on windows. The following instructions assume docker is installed on your box (or you are in docker VM if you are using docker tools such as boot2docker.
To perform testing on the latest checkins from development branch
Run simple configuration
Pull the web, nginx and db images on your box
$ docker pull goswamivijay/apiprototype-web-develop
$ docker pull goswamivijay/apiprototype-nginx-develop
$ docker pull goswamivijay/apiprototype-db-develop
Testing the application without nginx
Run database server
docker run -p 27017:27017 --name mymedlookupdb -d goswamivijay/apiprototype-db-develop
please note the container id that is displayed after you run the command, we will refer to it as the database container id.
Run web server
docker run -p 4000:4000 --name mymedlookupweb1 -d --link mymedlookupdb:mymedlookupdb goswamivijay/apiprototype-web-develop
please note the container id that is displayed after you run the command, we will refer to it as the web container id.
Navigate to http://<server address>:4000/ in your browser
To find the <server address> if you are running boot2docker, enter the following command
$ boot2docker ip
To stop the containers, run the following command
$ docker stop <web container id>
$ docker stop <db container id>
the web container id and the web container id are the ids that were diplayed when you used the run command. If you don't have the container id, you can query the conatiner id by running the following command
$ docker stop ps
The container id will be listed with the corresponding name of the container (mymedlookupweb1 for web and mymedlookupdb for database)
Run Production configuration
if you have already run the steps in Run simple configuration then you have to either remove the container using the following commands
$ docker rm <web container id>
$ docker rm <db container id>
or substitute the run commands with docker start command. The following instructions assume you haven't run the steps in Run simple configuration or you have removed the existing containers. i.e. you don't have any containers with same name either in running or stopped mode
Run database server
docker run -p 27017:27017 --name mymedlookupdb -d goswamivijay/apiprototype-db-develop
please note the container id that is displayed after you run the command, we will refer to it as the database container id.
Run web server - 1
docker run -p 4000 --name mymedlookupweb1 -d --link mymedlookupdb:mymedlookupdb goswamivijay/apiprototype-web-develop
please note the container id that is displayed after you run the command, we will refer to it as the web container id.
Run web server - 2
docker run -p 4000 --name mymedlookupweb2 -d --link mymedlookupdb:mymedlookupdb goswamivijay/apiprototype-web-develop
please note the container id that is displayed after you run the command, we will refer to it as the web container id.
Run nginx server
docker run -p 8090:80 --name mymedlookupproxy -d --link mymedlookupweb1:mymedlookupweb1 --link mymedlookupweb2:mymedlookupweb2 goswamivijay/apiprototype-nginx-develop
please note the container id that is displayed after you run the command, we will refer to it as the web container id.
Navigate to http://<server address>:8090/ in your browser
To find the <server address> if you are running boot2docker, enter the following command
$ boot2docker ip
To stop the containers, run the following command
$ docker stop <mymedlookupproxy container id>
$ docker stop <mymedlookupweb1 container id>
$ docker stop <mymedlookupweb2 container id>
$ docker stop <mymedlookupdb container id>
the web container id and the web container id are the ids that were diplayed when you used the run command. If you don't have the container id, you can query the container id by running the following command which will return stopped containers.
$ docker ps
To get a list of running containers, use the following command
$ docker ps
The container id will be listed with the corresponding name of the container (mymedlookupproxy for nginx server, mymedlookupweb1 for web and mymedlookupdb for database server)