Bump kafka client to fix snyk vulnerability #123
Draft
GitHub Actions / Tests
succeeded
Jan 8, 2025 in 0s
31 passed, 0 failed and 0 skipped
✅ target/test-reports/TEST-com.gu.mobile.content.notifications.lib.ContentAlertPayloadBuilderSpec.xml
17 tests were completed in 62ms with 17 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
com.gu.mobile.content.notifications.lib.ContentAlertPayloadBuilderSpec | 17✅ | 62ms |
✅ com.gu.mobile.content.notifications.lib.ContentAlertPayloadBuilderSpec
✅ Content Alert Payload Builder must create content alert for payload
✅ Content Alert Payload Builder must series tag should take precedence over the rest of the tags if there is only one
✅ Content Alert Payload Builder must use contributor name when a blog tag has the commentisfree id
✅ Content Alert Payload Builder must content tag should take precedence over contributor when generating web title
✅ Content Alert Payload Builder must use contributor for webtitle if there are no other relevant tags
✅ Content Alert Payload Builder must should use multiple contributor tags in web title if there is more than one
✅ Content Alert Payload Builder must should have no title if there are no followable tags
✅ Content Alert Payload Builder must use no imageUri if no image is found
✅ Content Alert Payload Builder must use imageUri when a valid main image is found
✅ Content Alert Payload Builder must do not prefix title for guardian-morning-briefing
✅ Content Alert Payload Builder must do not prefix title for first-edition
✅ Content Alert Payload Builder must do not prefix title for andrew-sparrows-election-briefing
✅ Content Alert Payload Builder must do not prefix title for guardian-australia-s-morning-mail
✅ Content Alert Payload Builder must do not prefix title for guardian-us-briefing
✅ Content Alert Payload Builder must should have a maximum of 3 topics
✅ create content alert for content & blogPost
✅ create content alert for content & blogPost without title
✅ target/test-reports/TEST-com.gu.mobile.content.notifications.lib.MessageSenderSpec.xml
4 tests were completed in 171ms with 4 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
com.gu.mobile.content.notifications.lib.MessageSenderSpec | 4✅ | 171ms |
✅ com.gu.mobile.content.notifications.lib.MessageSenderSpec
✅ Message Sender must record message success
✅ Message Sender must record message error
✅ Message Sender must properly deserialize a compressed event
✅ Message Sender must properly deserialize a non-compressed event
✅ target/test-reports/TEST-com.gu.mobile.content.notifications.lib.PayloadsSpec.xml
2 tests were completed in 849ms with 2 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
com.gu.mobile.content.notifications.lib.PayloadsSpec | 2✅ | 849ms |
✅ com.gu.mobile.content.notifications.lib.PayloadsSpec
✅ NotificationPayload should::define serializable Breaking News payload
✅ NotificationPayload should::define serializable Content Alert payload
✅ target/test-reports/TEST-com.gu.mobile.content.notifications.metrics.MetricsActorSpec.xml
8 tests were completed in 2s with 8 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
com.gu.mobile.content.notifications.metrics.MetricsActorSpec | 8✅ | 2s |
✅ com.gu.mobile.content.notifications.metrics.MetricsActorSpec
✅ The Metric Actor Logic should not call cloudwatch if there is not data
✅ The Metric Actor Logic should call cloudwatch once if there's one namespace with less than 20 points
✅ The Metric Actor Logic should call cloudwatch once but not aggregate if two metrics are received
✅ The Metric Actor Logic should call cloudwatch once if there's more than one metric
✅ The Metric Actor Logic should call cloudwatch as many times as we have namespaces
✅ The Metric Actor Logic should aggregate points into a MetricDatum
✅ The Metric Actor Logic should aggregate points into batches if there are more than 20 metrics per namespace
✅ The Metric Actor Logic should not aggregate points into multiple batches if there are 20 metrics or less per namespace
Loading