Created 5 feature files covering blog generation, scheduling, LLM provider selection, SEO population, and notification emails. These files define the Gherkin scenarios that pytest-bdd will generate test functions for. - blog_generation.feature: On-demand generation with auto-publish toggle - blog_scheduling.feature: Scheduled cron slot execution - llm_provider_selection.feature: Provider dispatch and error handling - seo_population.feature: SEO metadata and tag assignment - notification_email.feature: Email notifications after generation Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
22 lines
1 KiB
Gherkin
22 lines
1 KiB
Gherkin
Feature: Notification email after generation
|
|
As a content manager
|
|
I want to be notified when blog posts are generated and published
|
|
So that I can review and monitor content creation
|
|
|
|
Scenario: Notification email is sent after successful autopublish
|
|
Given the notification email recipient is "admin@itsulu.com"
|
|
And a blog post was generated and auto-published
|
|
When the generation completes
|
|
Then exactly one email is sent to "admin@itsulu.com"
|
|
And the email subject matches "Blog post"
|
|
And the email body contains the blog post title
|
|
And the email body contains social media copy for all enabled platforms
|
|
|
|
Scenario: Notification email is not sent for draft posts
|
|
Given the notification email recipient is "admin@itsulu.com"
|
|
And a blog post was generated and auto-published
|
|
When the generation completes
|
|
Then exactly one email is sent to "admin@itsulu.com"
|
|
And the email body contains the blog post title
|
|
And the generation duration is recorded
|
|
And the generation log record contains tokens_used > 500
|