Testing

Continous Integration

Why?

We used Continous Integration (CI) within our project due to the agile approach we have taken. The places where we are using CI include the vf-to-ubf and ubf-to-twilio packages.

Catching bugs early and automatically is critical for reducing the number of defects introduced into production, increasing the overall quality and efficiency, and shortening the feedback cycle which is incredibly important for a software that helps provide medical advice.

Running Continuous Integration

Using Github actions, we have it set up in a way where we run all unit and integration tests each time we push a new change or merge a pull request to the master branch.

Our CI tests also use Twilio test credentials which are hidden away using Github secrets. This allows CI to not only notify us of any bugs but also if any changes occur to the Twilio API.