Skip to content

Update sbt-assembly to 2.3.0 #328

Update sbt-assembly to 2.3.0

Update sbt-assembly to 2.3.0 #328

GitHub Actions / Tests succeeded Oct 7, 2024 in 0s

35 passed, 0 failed and 0 skipped

Tests passed successfully

Report Passed Failed Skipped Time
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.apns.models.payload.ApnsPayloadBuilderSpec.xml 10✅ 1s
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.FcmClientTest.xml 3✅ 4s
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.FcmTransporttJdkImplSpec.xml 4✅ 773ms
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.models.payload.FcmPayloadBuilderSpec.xml 6✅ 49ms
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.HarvesterRequestHandlerSpec.xml 1✅ 224ms
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.models.SendingResultsSpec.xml 8✅ 91ms
notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.SenderRequestHandlerSpec.xml 3✅ 8s

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.apns.models.payload.ApnsPayloadBuilderSpec.xml

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

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.delivery.apns.models.payload.ApnsPayloadBuilderSpec 10✅ 1s

✅ com.gu.notifications.worker.delivery.apns.models.payload.ApnsPayloadBuilderSpec

✅ ApnsPayload should::generate correct payload for Breaking News notification
✅ ApnsPayload should::generate correct payload for Breaking News notification with no thumbnail
✅ ApnsPayload should::generate correct payload for Breaking News notification with no image
✅ ApnsPayload should::generate correct payload for Liveblog notifications if blockId exists
✅ ApnsPayload should::generate correct payload for Breaking News notification with no title
✅ ApnsPayload should::generate correct payload for Content notification
✅ ApnsPayload should::generate correct payload for Match status notification
✅ ApnsPayload should::generate correct payload for Newsstand notification
✅ ApnsPayload should::generate correct payload for Edition notification
✅ ApnsPayload should::generate correct payload for US Election notification

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.FcmClientTest.xml

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

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.delivery.fcm.FcmClientTest 3✅ 4s

✅ com.gu.notifications.worker.delivery.fcm.FcmClientTest

✅ the FcmClient should::Parse successful responses as an FcmDeliverySuccess
✅ the FcmClient should::Parse errors with an invalid token error code as an InvalidToken
✅ the FcmClient should::Parse errors with NOT_FOUND error code and 'Requested entity was not found.' error message as an InvalidToken

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.FcmTransporttJdkImplSpec.xml

4 tests were completed in 773ms with 4 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.delivery.fcm.FcmTransporttJdkImplSpec 4✅ 773ms

✅ com.gu.notifications.worker.delivery.fcm.FcmTransporttJdkImplSpec

✅ FcmTransporttJdkImpl should::parse an invalid token error response correctly from from Firebase API
✅ FcmTransporttJdkImpl should::parse an unexpected error response with general details field from Firebase API
✅ FcmTransporttJdkImpl should::parse an internal error object from the error response without details field from Firebase API
✅ FcmTransporttJdkImpl should::handle unsupported error response from Firebase API gracefully

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.delivery.fcm.models.payload.FcmPayloadBuilderSpec.xml

6 tests were completed in 49ms with 6 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.delivery.fcm.models.payload.FcmPayloadBuilderSpec 6✅ 49ms

✅ com.gu.notifications.worker.delivery.fcm.models.payload.FcmPayloadBuilderSpec

✅ FcmPayload should::generate correct data for Breaking News notification
✅ FcmPayload should::generate correct data for Breaking News notification with no title
✅ FcmPayload should::generate correct data for Content notification
✅ FcmPayload should::generate correct data for Match Status notification
✅ FcmPayload should::generate correct data for Editions notification
✅ FcmPayload should::generate correct data for US Elections notification

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.HarvesterRequestHandlerSpec.xml

1 tests were completed in 224ms with 1 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.HarvesterRequestHandlerSpec 1✅ 224ms

✅ com.gu.notifications.worker.HarvesterRequestHandlerSpec

✅ the WorkerRequestHandler should::Queue one multi platform breaking news notification

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.models.SendingResultsSpec.xml

8 tests were completed in 91ms with 8 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.models.SendingResultsSpec 8✅ 91ms

✅ com.gu.notifications.worker.models.SendingResultsSpec

✅ LatencyMetrics.aggregateForCloudWatch should::Create a single batch of token delivery latencies if there are less than 150 unique values (and the default batch size is used)
✅ LatencyMetrics.aggregateForCloudWatch should::Create multiple batches of token delivery latencies if the number of items exceeds the batch size
✅ LatencyMetrics.aggregateForCloudWatch should::Create multiple batches of 150 by default
✅ LatencyMetrics.audienceSizeBucket should::Categorise a small audience correctly
✅ LatencyMetrics.audienceSizeBucket should::Categorise a medium audience correctly
✅ LatencyMetrics.audienceSizeBucket should::Categorise a large audience correctly
✅ LatencyMetrics.audienceSizeBucket should::Categorise an extra large audience correctly
✅ LatencyMetrics.audienceSizeBucket should::Mark a missing audience as unknown

✅ notificationworkerlambda/target/test-reports/TEST-com.gu.notifications.worker.SenderRequestHandlerSpec.xml

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

Test suite Passed Failed Skipped Time
com.gu.notifications.worker.SenderRequestHandlerSpec 3✅ 8s

✅ com.gu.notifications.worker.SenderRequestHandlerSpec

✅ the SenderRequestHandler should::Send one notification
✅ the SenderRequestHandler should::Clean invalid tokens
✅ the SenderRequestHandler should::Count dry runs