These don't each have to map to a different test. We can probably combine some by just treating the tests as "journeys". This is just a list of new functionality / code paths / use cases to cover.

• Creating a new connection from the sidebar. (already covered by existing tests because that's the way it always adds connections)
• Creating a new connection from the welcome page. (unit tests are probably fine?)
• Disconnecting from a cluster without tabs. (already covered by existing tests since we disconnect before connecting all the time)
• Disconnecting from a cluster with open tabs. (kinda covered, but not really asserted on yet since we also close all open tabs) (COMPASS-8151)
• Connecting to a cluster
  • Success (already covered)
  • Connection failure - can be reviewed via toast (mostly already covered, although we don't click the review button yet) (COMPASS-8151)
  • Multiple connection failures - all can be reviewed via toast (COMPASS-8153)
  • Connecting takes too long - can be cancelled via toast (COMPASS-8153)
  • Multiple connections taking too long - all can be cancelled via toast (COMPASS-8153)
• Opening a query on the My Queries page (COMPASS-8152)
  • when you have multiple active connections that have the namespace
  • when you have multiple active connections, and only one of them has the namespace
  • when you have multiple active connections, and none of them have the namespace
• Connect to two connections and switch between them (COMPASS-8151)
• Connect to two connections on different clusters, have the same database and collection names on both, import/export/bulk update/bulk delete/create index/create database/create collection on one, make sure it appears on the correct one (we can probably adjust existing tests for those by just having the second connection active too) (COMPASS-8151)