✅ Integration Test Reports — Help us verify adapters you have access to #3
Unanswered
RecurPixel
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Why this discussion exists
RecurPixel.Notify ships with unit tests for every adapter, but integration testing requires
real API keys for every provider — and it is not possible for the core team to hold active
accounts and paid credentials for every platform.
This is where the community comes in.
If you have access to a provider — Twilio, FCM, AWS SNS, Vonage, or anything else —
you can run the integration test for that specific adapter in under 5 minutes and post
your results here. Verified reports get marked as ✅ Community Verified in the official
adapter docs and README.
Current Verification Status
Email.SendGridEmail.SmtpEmail.MailgunEmail.ResendEmail.PostmarkEmail.AwsSesEmail.AzureCommEmailSms.TwilioSms.VonageSms.PlivoSms.SinchSms.MessageBirdSms.AwsSnsSms.AzureCommSmsPush.FcmPush.ApnsPush.OneSignalPush.ExpoWhatsApp.TwilioWhatsApp.MetaCloudWhatsApp.VonageSlackDiscordTeamsMattermostRocketChatFacebookTelegramLineViberInAppLegend: ✅ Complete · 🔲 Not yet ·⚠️ Partial
This table is updated as reports are verified and approved.
How to Run the Integration Tests
All integration tests live in a single project — one test class per adapter, all sharing
the same configuration file.
Step 1 — Clone the repo and navigate to the integration test project
git clone https://github.com/recurpixel/notify.git cd notify/tests/RecurPixel.Notify.IntegrationTestsStep 2 — Fill in your credentials
Copy the template and fill in only the providers you have access to. Every field you leave
blank is automatically skipped — that adapter's test will be marked as skipped, not failed.
Then open
appsettings.integration.jsonand fill in your credentials:{ "_readme": "Fill in the credentials for providers you want to test. Leave any field blank to skip that adapter automatically. NEVER commit this file — it is git-ignored.", "Integration": { "ToEmail": "your-test-inbox@example.com", "ToPhone": "+1234567890", "ToDeviceToken": "", "ToWhatsApp": "", "ToSlack": "", "ToTelegram": "" }, "Notify": { "Sms": { "Twilio": { "AccountSid": "ACxxx", "AuthToken": "xxx", "FromNumber": "+0987654321" } } } }You only need to fill in the sections relevant to what you are testing. Everything else
can stay blank or be omitted entirely.
Step 3 — Run only the adapter you want to test
Each adapter has its own test class. Run it by fully qualified name so you only execute
what you have credentials for:
Or run everything you have configured in one go — any adapter with blank credentials
is skipped automatically:
dotnet testHow to Submit a Report
Post a reply in this thread using the following template:
Once reviewed by the core team your adapter gets marked ✅ Community Verified and
your GitHub profile is credited in the verification entry.
Ground Rules
Why This Matters
Every ✅ on that table is a signal to the next developer evaluating this library that the
adapter works in production, not just in mocked unit tests. The more providers the community
verifies, the more trustworthy the library becomes for everyone.
If an adapter has been sitting at ⏳ for a long time and you have access to that provider —
please test it. It takes less than 10 minutes and it helps every future user of that provider.
Drop your report below 👇
Beta Was this translation helpful? Give feedback.
All reactions