Detail plan for implementing CI (continuous integration) - Githubissues

tekuma / curator-portal

Interface for the Curation database

0 stars 0 forks source link

Detail plan for implementing CI (continuous integration) #64

Closed xstephen95x closed 7 years ago

xstephen95x commented 7 years ago

Detail a plan to use a CI service.

Options:

GCE Instace running jenkins
TravisCI (69$/month for 1 service)

xstephen95x commented 7 years ago

In meeting on 1 Feb, scott kun and stephen all supported the idea of using TravisCI

slivingston commented 7 years ago

Travis CI, https://travis-ci.com/plans
CircleCI, https://circleci.com/pricing/

slivingston commented 7 years ago

we are trying Travis CI now. https://travis-ci.com/tekuma/curator-portal/builds/39640320

slivingston commented 7 years ago

I have demonstrated end-to-end testing locally on a Debian GNU/Linux box. Repeating in a Travis CI configuration is my next task.

slivingston commented 7 years ago

for extensive user-agent testing, we should eventually consider products from Sauce Labs http://saucelabs.com/pricing. However, I do not think that it is yet well motivated, given the relatively small variety in manners of access to the curator-portal website and, furthermore, because the UI is still undergoing substantial changes.

slivingston commented 7 years ago

as of commit dce7f0f1414a9a59486d686ee43fd5b3258013f9, end-to-end testing is operational as part of CI. The first demonstrating test is a trivial click-and-check interaction with the home button on the curator-portal log-in page.