Technical debt:

• eLife recognised that lack of automated testing should be addressed 

Test strategy:

• Digirati came up with a test strategy that put emphasis of both unit tests and end to end tests in their scenario  

Unit tests

• Run faster 
• Locally
• Enables us to fix bugs quickly

End-to-end tests

• Integration of all their systems that talk to each other for the full functioning of Continuum 

eLife bot

• Unit tests at the activity level

eLife dashboard

• Tests written at the API level

End-to-end tests

• End-to-end pipeline built was led by a test engineer @ eLife
• Built on Jenkins together with their own automated deployment platform

Open sourcing

• eLife bot has been open source since its launch
• eLife dashboard was open sourced after the API testing coverage was applied
• eLife has hosted a Webinar introducing the Continuum open sourced project with an attendance of 110+ people

eLife 2.0

• major changes in their architecture
•  JSON article standard
• Looking into IIIF