Goals

• A better understanding of the CollectionsStore before all hook within the Compass unit test suite, e.g. How does the mock data service work?
• An estimate or probability - How likely it is to hit the 2000ms time limit?
• An explanation of how the 2000ms (or more) of time is spent
• Recommendations or proof-of-concepts which may resolve this issue

If time allows, PR and fix this test issue, if not, create a follow up ticket with any proposed future work.

As this ticket is a spike and focused on exploring - ideas are always welcome

Rationale

As noted on COMPASS-2159, Travis build failures usually require the developer to manually retry the build, which as technical debt slows down the team's capacity to deliver new features and bug fixes.

Example error output

  1) CollectionsStore "before all" hook:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.

List of known red jobs

https://travis-ci.com/10gen/compass/jobs/89073210
https://travis-ci.com/10gen/compass/jobs/89088573
https://travis-ci.com/10gen/compass/jobs/93094619
https://travis-ci.com/10gen/compass/jobs/93096547

1.9-releases is also known to be affected, so a fix should be backported to supported Compass versions:
https://travis-ci.com/10gen/compass/jobs/93287442