Testing the notification center is slightly more involved as it requires a pattern of project dependency that first runs a Notifier test flow and follows that with a Recipient test. The notifier is responsible for performing actions that generate certain notifications for the recipient and the recipient is responsible for verifying they have received the notifications.

Tests can be run with the following commands:

yarn test:e2e --project "Notifications Owner as Notifier" \\
	"Notifications Collaborator as Recipient"
yarn test:e2e --project "Notifications Collaborator as Notifier" \\
	"Notifications Owner as Recipient"

Loom with more in-depth walkthrough of the test pattern:

https://www.loom.com/share/dc68ef4390114e08b83b2f8b3831c95a

There are some notifications that are hard to test right now for various reasons given the patterns of needing to ping/pong between notifier and recipient (user A / user B) test runs in order to fully cover certain outcomes:

• Right now testing PRIMARY_PLAN_READY notifications that would require turking OR faking turking of a the blueprint and that is just beyond scope right now 🤔
• Other kinds of notifications would be very cumbersome to test because you would need to chain project dependencies at least three deep in order to validate these things:
  • COMMENT_REPLY
  • COMPLETED_TASK
  • RESOLVED_THREAD
  • RESOLVED_COMMENT