0
Dry Runs
Source: knadh/listmonk#3238 · opened by @TomorrowToday
Problem*
I'm transitioning automated emails from another system to a listmonk server. I have tests for my code, but no easy way to prove the listmonk server accepts and processes the API requests without actually making changes or sending emails.
Solution
An optional dryrun parameter for API requests that aren't strictly reads. This would make integration testing much easier.
Work-around
I currently use a test-group list for emails so only a few people get each campaign that goes out. For Transactional emails, I'll write some custom tests to send out batches of emails to the test-group--not difficult, but a bit tedious. Subscriber and List API stuff probably need a couple tests to verify writes actually write what they're supposed to.
I'm transitioning automated emails from another system to a listmonk server. I have tests for my code, but no easy way to prove the listmonk server accepts and processes the API requests without actually making changes or sending emails.
Solution
An optional dryrun parameter for API requests that aren't strictly reads. This would make integration testing much easier.
Work-around
I currently use a test-group list for emails so only a few people get each campaign that goes out. For Transactional emails, I'll write some custom tests to send out batches of emails to the test-group--not difficult, but a bit tedious. Subscriber and List API stuff probably need a couple tests to verify writes actually write what they're supposed to.
No pledges yet. Be the first to back this.
No comments yet.