Also checkout these doc:

Guide: Testing Notification Center

Guide: The State of E2E

Test Setup

There are currently two ways to create a user session for a test:

1. Digs test fixtures (legacy)
2. Project dependencies (global setup)

Historically the Digs test fixtures were used for all tests, however this pattern relies on creating a brand new user, session and project for every single test that runs which is less than ideal.

When authoring any new tests we need to pick a path for the test to assume. Ideally any brand new test suites would be using the global setup method and older tests migrated to the global setup pattern as applicable.

Using the global setup pattern we can create a single user session and project for an entire suite of tests and even for all our tests at some point. This is highly desirable because it speeds up the total time it takes tests to run overall in several ways:

• Tests don’t have to create a new user/session/project each time which adds redundant time to all tests currently using the Digs test fixtures.
• Tests can be split up into smaller, more focused tasks creating faster individual tests in general that are easier to debug.
• Tests can be optimized to run fully parallel to speed up total test time across the board.