Testing Checklist

Please refer to the following test points during testing to ensure that the functionality and experience of each phase meet expectations.

I. Initialize the TopOn SDK at App Launch

• If publishing in the EU region, execute the GDPR compliance popup process before initializing the TopOn SDK.
• Clearly identify which ad networks are integrated (e.g., AdMob, Meta, etc.) and verify that each ad network's SDK is correctly integrated.

---

II. Preload Ads After SDK Initialization

• Execute ad loading logic at staggered times to avoid high-concurrency simultaneous ad loading requests.
• Reuse the same ad instance object globally for Rewarded Video, Interstitial, Splash, and Native Ad formats.

---

III. Rewarded Video & Interstitial Ads

• Initiate the first load request in advance after the TopOn SDK initialization is complete or upon entering the app's home page scenario.
• Call isReady before displaying the ad to check if it is available for display. If true, display it; if false, request to load the ad.
• Rewards for Rewarded Video must be granted in the onReward callback. Test whether the reward can be successfully granted.
• After the ad is dismissed, call load in the dismiss callback to preload the ad.
• Prevent multiple clicks: When displaying a Rewarded Video or Interstitial ad, prevent multiple clicks to avoid repeatedly showing the ad.

---

IV. Splash Ad

• If there is custom timeout logic, pass the same timeout duration to the TopOn SDK.
• If the load times out, navigate to the app's home page; if it does not time out, display the ad in the onAdLoaded callback.
• Preload in onAdDismiss for warm-start splash.
• When the app switches to the background or switches pages, call isReady to check if there is an available cache. If false, preload.
• Verify that the onAdDismiss callback is normal when clicking skip, and that external browser/app navigation is normal.

---

V. Banner Ad

---

VI. Native Ad

• If the NativeAd obtained in the onNativeAdLoaded callback is not null, save the reference for subsequent ad display.
• Self-Rendering: Each asset in SelfRenderView needs to be bound for rendering. Pay attention to whether onAdImpressed is triggered correctly.
• Resource release: When using NativeAd instances globally, release resources when the app exits. When bound to an Activity, call NativeAd.destroy() in onDestroy().
• Different platforms have different rendering requirements. Ensure that all ad networks can normally fill, display, and trigger the onAdImpressed callback.

---

VII. TopOn SDK Debug Log

Suggestion: For the waterfall configuration of each placement, make sure that the ad sources of each third-party ad network have been tested for normal fill and display before releasing the app.

---