- Split monolithic blog_generation.feature into separate files per feature: * blog_generation.feature: On-demand AI blog generation (3 scenarios) * blog_scheduling.feature: Scheduled posts (2 scenarios) * llm_provider_selection.feature: Multi-provider routing (6 scenarios) * seo_population.feature: SEO field population (1 scenario) * notification_email.feature: Post-generation emails (2 scenarios) Total: 14 BDD scenarios covering all major workflows - Extended test_bdd_steps.py from 363 to 472 lines with new step definitions: * Added no_email_sent() for draft post email suppression verification * Added email_contains_title() for email content validation * Added email_contains_social_copy() for platform copy verification * Added blog_post_has_tags(), blog_post_has_tag() for tag verification * Added blog_post_has_social_copy(), at_least_one_platform_enabled() * Added log_has_correct_provider(), log_has_correct_model() * Added log_trigger_source(), generation_duration_recorded() Follows pytest-bdd best practices: one feature per file, each with dedicated scenarios and step definitions. All 14 scenarios now have complete step coverage. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
19 lines
873 B
Gherkin
19 lines
873 B
Gherkin
# =================================================================
|
|
# SEO fields populated on every generated blog post
|
|
# =================================================================
|
|
Feature: SEO fields populated on every generated blog post
|
|
As an ITSulu content admin
|
|
I want all SEO fields filled automatically
|
|
So that every post is search-engine ready at publication
|
|
|
|
Background:
|
|
Given the Anthropic API key is configured in Settings
|
|
And the blog "ITSulu Insights" exists in Odoo
|
|
|
|
Scenario: All SEO fields are populated after generation
|
|
Given I am on the Blog Publisher backend form
|
|
And I enter topic "AI Governance Enterprise"
|
|
And I set auto-publish to True
|
|
When I click "Generate Now"
|
|
Then the SEO fields website_meta_title and website_meta_description are populated
|
|
And a generation log entry exists with state "success"
|