Test Suite

The DT FairBid Test Suite allows you to check that your app is set up correctly and ready to mediate using DT FairBid mediation. It checks that the mediated networks associated with the app are fully integrated, that Placements and Instances are correctly set up, and that ads are successfully served.

Launching the Test Suite

The Test Suite runs the following diagnostic tests when it launches:

• Mediated Networks Integration Status: Verifies whether mediated networks are properly integrated and ready to serve ads.

• Placements: Verifies whether all configured Placements and Instances in the DT Console are correctly set up and run as expected by DT FairBid's auction on real-time ad requests.

Launching the Test Suite via SDK

To launch the Test Suite via SDK or start the app in debug mode:

Android

1. Initialize the FairBid SDK and import the com.fyber.fairBid-sdk-plugin header.

2. Run the following API:

Java

FairBid.showTestSuite(activity);

iOS

Unity

Launch the Test Suite from Your App

You can launch the Test Suite from your app in Debug mode (signed with a Debug certificate). If the FairBid SDK detects integration errors, a pop-up message appears. No explicit SDK call is required.

To launch the Test Suite from your app:

1. Sign your app with a Debug certificate, and start your app. If the FairBid SDK detects integration errors, a pop-up that summarizes the errors found automatically appears.

Test Suite pop-up for App in Debug mode

The FairBid SDK displays this pop-up only when your app is in debug mode. The FairBid SDK turns off this pop-up when you sign your app with a release certificate.

1. Tap Test Suite. The Test Suite opens with additional diagnostic details.

Mediated Networks Integration Status

The main screen of the Test Suite gives you an immediate idea of your mediated network's integration status:

• Successful Integration: A green screen indicates that the associated mediated networks are connected and enabled. For more information about how to test the instances in your app, see Testing Mediated Network Instances.

• Unsuccessful Integration: A red screen indicates that the Test Suite encountered errors while attempting to connect to your mediated networks. Tap the red square for more information about the mediation errors. DT recommends correcting the identified issues before going live with your app.

SUCCESSFUL INTEGRATION	UNSUCCESSFUL INTEGRATION

Troubleshooting Integration Errors

If the Test Suite detects an integration error, it provides information to help you identify and fix the issue. Some common errors and suggested fixes include:

Missing SDK

Android

ISSUE DESCRIPTION	SUGGESTED FIX
The DT FairBid SDK requires the mediated ad network's SDK to work. If the Test Suite mentions that a network is missing its SDK, then it might mean you forgot to insert the network's SDK into your project.	Refer to the documentation on integrating that specific network into your project to resolve this problem.
If the AdMob SDK is not implemented or configured in the Console but the Google Play Services API is still used in the project, the following error occurs when you integrate AdMob.	This message only applies to AdMob integrations. If you are not planning to integrate AdMob, you can ignore this error message.

iOS

Unity

Not Configured in the Console

ISSUE DESCRIPTION	SUGGESTED FIX
DT FairBid SDK requires enabling the mediated ad networks in the console. If the Test Suite mentions that a network is not configured in the console, you might have forgotten to enable it and configure it for your application in the console.	Refer to the documentation on integrating that specific network into your project to resolve this problem.

Missing Credentials

ISSUE DESCRIPTION	SUGGESTED FIX
For the mediation stack of the DT FairBid SDK to work, the SDK needs to have access to your credentials for the different networks you integrate. If the Test Suite mentions that a network is missing credentials, it was not configured with credentials in the Console.	Access the Console and verify that credentials are correctly configured for the relevant network to resolve this issue.

Missing Activities

Android

Not applicable.

iOS

Unity

Missing Permissions

Android

Not applicable.

iOS

Unity

Testing Mediated Network Instances

After integrating the mediated networks, use the Test Suite to request and display ads:

1. Tap the green square on the main menu.

2. Select the network you want to interact with from the list of networks.

3. View the list of configured Instances in your app:

• Mediation Placements (waterfall instances).

• Programmatic Mediation Placements (bidding instances).

Waterfall Instances

The Waterfall Instances section lists all Instances configured in the Console. Tap Request and Show to request and show ads for these Instances.

Bidding Instances

This section lists all the bidding Instances configured in the Console and used throughout your app.

Placements

The Placements section of the Test Suite allows you to validate placement setups and view performance details:

• Verify that the Placements Instances setup is applied correctly as configured in the Console.

• View the order of a Placement's Waterfall Instances, which includes CPM values predicted by the DT FairBid algorithm when you select Auto CPM in the Console.

• Request an ad and see in real-time how the DT FairBid auction selects a winner.

Verify Placement Instance Setup

To view and verify the configured placements for your app:

1. Tap the Placement section of the main screen (the blue square). The Placements, including the Placement name, ID, and Type, appear.

2. To view the bidding Instances set for the placement, tap on a placement. For each Instance, the following information appears:

• Mediated Network name.

• Instance ID: Configured on the mediated network's dashboard and set in the DT Console.

• Predicted CPM Value:

  • Auto CPM: The predicted value by DT FairBid's algorithm appears.

  • Manual CPM: The value appears in bold, alongside the predicted value by FairBid's algorithm if available.

    The Instance is positioned in the waterfall by the CPM values in bold.

Running the DT FairBid Auction

To run the DT FairBid auction and verify that the Placement delivers ads successfully and instances are called as expected:

1. Tap Request (Show for banner placements) button. The DT FairBid auction starts running and looks for available ads from the Waterfall instances. If necessary, it proceeds to the bidders' auction to find a bid that meets the Placement floor price or beats the Waterfall result.

2. The Auction status appears at the bottom of the screen while the auction is running. Once the auction ends, the winning Instance appears.

3. To view the winning ad, tap Show.

Waterfall Instance Responses

RESPONSE	DESCRIPTION
Requesting	Requesting an ad for the Instance.
Fill	Instance returns an ad.
No Fill	Instance reports that no ad is available.
Instance Timeout	Instance does not respond in time, but the SDK is still awaiting a response.
Failure	An error occurred during the Instance request, such as adapter failure, error, or timeout.

Troubleshooting

Requesting an ad can sometimes fail for many reasons. Below is a list of possible problems to check that can help you get an ad:

PROBLEM	RESOLUTION
Console Credentials	Verify correct credentials and mediation placements.
Console Logs	Review console logs for network-specific warnings or integration notes.
Network Documentation	Confirm correct SDK integration and required settings, including test device setup and test ad configuration.

Caching Mechanism

The DT FairBid SDK implements a caching mechanism for the console configuration. As a result, you might experience some delays when you change your console configuration and when the changes reflect in the SDK. DT recommends deleting and reinstalling your application after every change in the Console.