Skip to content

SDKS-4716: Fix for Push Notification E2E test#168

Closed
vibhorgoswami wants to merge 1 commit intodevelopfrom
SDKS-4716_UI_Test_Fix
Closed

SDKS-4716: Fix for Push Notification E2E test#168
vibhorgoswami wants to merge 1 commit intodevelopfrom
SDKS-4716_UI_Test_Fix

Conversation

@vibhorgoswami
Copy link
Contributor

JIRA Ticket

SDKS-4716

Description

Fixes the PushNotification association with PushCredential. Enhance PushDeviceToken initialization with optional ID handling.

Testing

  • Tested on Pull Request which has the E2E test cases.
  • Migration push notification testing using PUSH-AUTH journey

@vibhorgoswami vibhorgoswami self-assigned this Mar 4, 2026
@codecov
Copy link

codecov bot commented Mar 5, 2026

Codecov Report

❌ Patch coverage is 0% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 44.88%. Comparing base (74b0a2f) to head (5585f78).

Files with missing lines Patch % Lines
...tity/auth/migration/AuthenticatorMigrationSteps.kt 0.00% 20 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #168      +/-   ##
=============================================
- Coverage      44.92%   44.88%   -0.04%     
  Complexity      1232     1232              
=============================================
  Files            302      302              
  Lines           9389     9401      +12     
  Branches        1352     1358       +6     
=============================================
+ Hits            4218     4220       +2     
- Misses          4630     4642      +12     
+ Partials         541      539       -2     
Flag Coverage Δ
integration-tests 25.96% <0.00%> (-0.03%) ⬇️
unit-tests 26.19% <0.00%> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

credentialId = notificationData["credentialId"]?.jsonPrimitive?.content ?: "",
credentialId = notificationData["credentialId"]?.jsonPrimitive?.content
?: notificationData["mechanismUID"]?.jsonPrimitive?.content
?: "",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we try to get credentialId first, if not exist we get the mechanismUID, any reason for this scenario? Do you see the legacy set the id either in this 2 attributes?

Similar for other attributes mapping, we try to find if data exist on one attribute, if not found try another, not sure if this is correct.

@vibhorgoswami vibhorgoswami deleted the SDKS-4716_UI_Test_Fix branch March 5, 2026 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants