Skip to content
GitHub Actions / Tests succeeded Sep 26, 2024 in 1s

21 passed, 0 failed and 0 skipped

Tests passed successfully

Report Passed Failed Skipped Time
notification/target/test-reports/TEST-notification.controllers.MainSpec.xml 12✅ 240ms
notification/target/test-reports/TEST-notification.services.ArticlePurgeSpec.xml 2✅ 421ms
notification/target/test-reports/TEST-notification.services.frontend.FrontendAlertsSpec.xml 2✅ 2s
notification/target/test-reports/TEST-notification.services.guardian.GuardianNotificationSenderSpec.xml 5✅ 414ms
notification/target/test-reports/TEST-notification.services.NewsstandSenderTest.xml 0ms

✅ notification/target/test-reports/TEST-notification.controllers.MainSpec.xml

12 tests were completed in 240ms with 12 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
notification.controllers.MainSpec 12✅ 240ms

✅ notification.controllers.MainSpec

✅ Sending notification to topics should::successfully send a notification to multiple topics
✅ Sending notification to topics should::refuse a notification with an invalid key
✅ Sending notification to topics should::refuse a notification that is sent twice
✅ Sending notification to topics should::refuse a notification without a topic
✅ Sending notification to topics should::refuse a notification with too many topics
✅ Sending notification to topics should::fail gracefully for non-fatal errors
✅ adding a new notification topic should::successfully add a new topic and send a notification to it
✅ removing a new notification topic should::successfully remove a topic and stop sending notifications to it
✅ Sending correct notification should::notify reporting repository about added notifications
✅ Sending notification for newsstand should::successfully send a notification for newsstand
✅ Sending notification for newsstand should::refuse a newsstand notification with an invalid key
✅ Sending notification for newsstand should::Send a newstand notification shard

✅ notification/target/test-reports/TEST-notification.services.ArticlePurgeSpec.xml

2 tests were completed in 421ms with 2 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
notification.services.ArticlePurgeSpec 2✅ 421ms

✅ notification.services.ArticlePurgeSpec

✅ ArticlePurge should::trigger a soft purge for a breaking news
✅ ArticlePurge should::do nothing for any other notification type

✅ notification/target/test-reports/TEST-notification.services.frontend.FrontendAlertsSpec.xml

2 tests were completed in 2s with 2 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
notification.services.frontend.FrontendAlertsSpec 2✅ 2s

✅ notification.services.frontend.FrontendAlertsSpec

✅ Frontend alerts notified about notification should::skip breaking news notification without capi id (i.e. with non-internal Link)
✅ Frontend alerts notified about notification should::successfully send notification

✅ notification/target/test-reports/TEST-notification.services.guardian.GuardianNotificationSenderSpec.xml

5 tests were completed in 414ms with 5 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
notification.services.guardian.GuardianNotificationSenderSpec 5✅ 414ms

✅ notification.services.guardian.GuardianNotificationSenderSpec

✅ GuardianNotificationSender should::prepare shards with inclusive bounds
✅ GuardianNotificationSender should::put batches messages on the queue
✅ GuardianNotificationSender should::put many batches messages on the queue for popular topics
✅ GuardianNotificationSender should::put many batches messages on the queue, even if the topic counter fails
✅ GuardianNotificationSender should::return an error if one of the batches couldn't be pushed to the queue

✅ notification/target/test-reports/TEST-notification.services.NewsstandSenderTest.xml

No tests found

Test suite Passed Failed Skipped Time
notification.services.NewsstandSenderTest 0ms