teads_flutter_mocks library

Test doubles for package:teads_flutter's injectable interfaces.

Import this separately from package:teads_flutter/teads_flutter.dart — deliberately not re-exported from there, so production code never pulls in test scaffolding. Install a mock by assigning it to the corresponding static .instance:

TeadsSdk.instance = MockTeadsSdk();
TeadsPrivacy.instance = MockTeadsPrivacy();
Recommendations.instance = MockRecommendations(recommendations: [...]);
final interstitial = MockInterstitial(); // constructed directly, not via .instance

MockInterstitial stands in for an Interstitial your own code constructs and holds — InterstitialPlacement itself has no injectable instance to swap, since it isn't a singleton the way TeadsSdk/ TeadsPrivacy/Recommendations are. MockBannerController extends the concrete BannerController (not just BannerApi), so it substitutes directly into BannerPlacement.controller for a widget test, unlike the other mocks here which stand in for an interface. There is no Media mock: Media has no injectable interface — see docs/integration-usage.md's section on "Depending on an interface" for why.

FeedPlacement is different again: it has no injectable interface and never will (it builds its own real WebViewController internally, and webview_flutter's platform view cannot run in flutter test at all). MockFeedPlacement mirrors its constructor/callbacks exactly instead, and FeedPlacementBuilder is the seam that lets a test substitute one for the other — see both types' doc comments.