feat(smoke-tests): test auto-updating from the version of Compass that was just packaged COMPASS-8536 #6629
Conversation
| env.UPDATE_CHECKER_ALLOW_DOWNGRADES = 'true'; | ||
| } | ||
|
|
||
| // a git repo that is not published to npm that evergreen clones for us in CI |
There was a problem hiding this comment.
I don't know how best to cleanly start this, especially in dev. This assumes that compass-mongodb-com is cloned right next to compass which is hacky.
My initial plan was to start the server using docker in evergreen so it is already running before we execute the smoke tests, but we don't have docker in every platform where we want to run the smoke tests, so I think we have to start the server manually.
Furthermore we'll also have two of these servers with different configuration that we'll need back-to-back because updating from the most recent release TO this test subject will require telling the auto-update server about this new unreleased copy of compass.
|
|
||
| describe('Auto-update', function () { | ||
| it('auto-update from', async function () { | ||
| if (process.env.TEST_NAME !== 'AUTO_UPDATE_FROM') { |
There was a problem hiding this comment.
Open to ideas for a better name for this env var. I think we'll also have AUTO_UPDATE_TO once we add that test next to this one. These tests kinda have to be the only test you run at a time because they replace the test subject.
lerouxb
force-pushed
the
autoupdate-from3
branch
from
c9c0779 to
de07d7f
Compare
Replaces #6608
Requires #6625, so merge that first.