8000 Fix: Added notificationRegistry to make sure that odpSettings updates by mnoman09 · Pull Request #501 · optimizely/java-sdk · GitHub
[go: up one dir, main page]

Skip to content

Fix: Added notificationRegistry to make sure that odpSettings updates #501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 20 commits into from
Jan 26, 2023
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Added suppress warning
  • Loading branch information
NomanShoaib committed Jan 11, 2023
commit 51357cf8841f6aaa064e34fd4776ecc75fb5d66a
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,16 @@
package com.optimizely.ab.internal;

import com.optimizely.ab.notification.NotificationCenter;
import edu.umd.cs.findbugs.annotations.SuppressFBWarnings;
import org.junit.Assert;
import org.junit.Test;

import static org.junit.Assert.assertEquals;


public class NotificationRegistryTest {

@SuppressFBWarnings("NP_NONNULL_PARAM_VIOLATION")
@Test
public void getSameNotificationcenterWhenSDKkeyIsNull() {
String sdkKey = null;
Expand All @@ -40,6 +43,7 @@ public void getSameNotificationcenterWhenSDKkeyIsSameButNotNull() {
assertEquals(notificationCenter1, notificationCenter2);
}

@SuppressFBWarnings("NP_NONNULL_PARAM_VIOLATION")
@Test
public void getSameNotificationcenterWhenSDKkeyIsNullAndAnotherIsEmpty() {
String sdkKey1 = "";
Expand Down
0