🧪 Unit Test Results

1188

Passed

Failed

1188

Total

22.97s

Duration

Test Suites

✅ agentic-workflow-mcp-queries.test.js

✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-evening-analysis.md should document get_sync_status() call
✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-evening-analysis.md should warn about stale data
✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-article-generator.md should document get_sync_status() call
✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-article-generator.md should warn about stale data
✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-realtime-monitor.md should document get_sync_status() call
✅ Agentic Workflow MCP Query Patterns Data Freshness Validation news-realtime-monitor.md should warn about stale data
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-evening-analysis.md should document explicit date parameters
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-evening-analysis.md should NOT rely on implicit "latest" patterns
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-article-generator.md should document explicit date parameters
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-article-generator.md should NOT rely on implicit "latest" patterns
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-realtime-monitor.md should document explicit date parameters
✅ Agentic Workflow MCP Query Patterns Explicit Date Filtering news-realtime-monitor.md should NOT rely on implicit "latest" patterns
✅ Agentic Workflow MCP Query Patterns Post-Query Date Filtering Documentation news-evening-analysis.md should document post-query filtering
✅ Agentic Workflow MCP Query Patterns Post-Query Date Filtering Documentation workflows should annotate tools with date support
✅ Agentic Workflow MCP Query Patterns Cross-Referencing Strategy news-evening-analysis.md should have cross-referencing examples
✅ Agentic Workflow MCP Query Patterns Error Handling news-evening-analysis.md should document error scenarios
✅ Agentic Workflow MCP Query Patterns Error Handling news-evening-analysis.md should document stale data handling
✅ Agentic Workflow MCP Query Patterns Error Handling news-article-generator.md should document error scenarios
✅ Agentic Workflow MCP Query Patterns Error Handling news-article-generator.md should document stale data handling
✅ Agentic Workflow MCP Query Patterns Error Handling news-realtime-monitor.md should document error scenarios
✅ Agentic Workflow MCP Query Patterns Error Handling news-realtime-monitor.md should document stale data handling
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-evening-analysis.md should list all 32 riksdag-regering tools
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-evening-analysis.md should emphasize get_sync_status() first
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-article-generator.md should list all 32 riksdag-regering tools
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-article-generator.md should emphasize get_sync_status() first
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-realtime-monitor.md should list all 32 riksdag-regering tools
✅ Agentic Workflow MCP Query Patterns MCP Tool Documentation Quality news-realtime-monitor.md should emphasize get_sync_status() first
✅ Agentic Workflow MCP Query Patterns Date Filtering Best Practices workflows should have date calculation examples
✅ Agentic Workflow MCP Query Patterns Date Filtering Best Practices workflows should document riksmöte (rm) parameter usage
✅ Agentic Workflow MCP Query Patterns Workflow Compilation news-evening-analysis.md should compile without errors
✅ Agentic Workflow MCP Query Patterns Workflow Compilation news-article-generator.md should compile without errors
✅ Agentic Workflow MCP Query Patterns Workflow Compilation news-realtime-monitor.md should compile without errors
✅ Agentic Workflow MCP Query Patterns Regression Prevention evening analysis should maintain enhanced query patterns
✅ Agentic Workflow MCP Query Patterns Regression Prevention workflows should not use ambiguous "latest" language
✅ MCP Tool Date Parameter Support Matrix should document which tools support date parameters

✅ article-template.test.js

✅ Article Template generateArticleHTML should generate valid HTML structure
✅ Article Template generateArticleHTML should include article title in multiple locations
✅ Article Template generateArticleHTML should include SEO meta tags
✅ Article Template generateArticleHTML should include hreflang tags for bilingual support
✅ Article Template generateArticleHTML should include Schema.org structured data
✅ Article Template generateArticleHTML should include event calendar section
✅ Article Template generateArticleHTML should include watch section
✅ Article Template generateArticleHTML should include article content
✅ Article Template generateArticleHTML should include proper CSS classes for styling
✅ Article Template generateArticleHTML should support Swedish language
✅ Article Template generateArticleHTML should use external styles.css and not embed CSS
✅ Article Template generateArticleHTML should include accessibility attributes
✅ Article Template generateArticleHTML should include sources attribution
✅ Article Template generateArticleHTML should include back to news link
✅ Article Template Default export should export generateArticleHTML, generateEventCalendar, generateWatchSection
✅ Article Template Multi-language type labels should use correct type label for en/prospective
✅ Article Template Multi-language type labels should use correct type label for sv/prospective
✅ Article Template Multi-language type labels should use correct type label for da/analysis
✅ Article Template Multi-language type labels should use correct type label for no/breaking
✅ Article Template Multi-language type labels should use correct type label for fi/retrospective
✅ Article Template Multi-language type labels should use correct type label for de/prospective
✅ Article Template Multi-language type labels should use correct type label for fr/breaking
✅ Article Template Multi-language type labels should use correct type label for es/analysis
✅ Article Template Multi-language type labels should use correct type label for nl/prospective
✅ Article Template Multi-language type labels should use correct type label for ar/prospective
✅ Article Template Multi-language type labels should use correct type label for he/breaking
✅ Article Template Multi-language type labels should use correct type label for ja/prospective
✅ Article Template Multi-language type labels should use correct type label for ko/analysis
✅ Article Template Multi-language type labels should use correct type label for zh/breaking
✅ Article Template Multi-language type labels should fall back to English type label for unknown language
✅ Article Template Multi-language type labels should show News for unknown type
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for en
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for sv
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for da
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for no
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for fi
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for de
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for fr
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for es
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for nl
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for ar
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for he
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for ja
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for ko
✅ Article Template Footer labels / localized back-to-news link should use localized back-to-news for zh
✅ Article Template Breadcrumb translations should include Home and News breadcrumbs in English
✅ Article Template Breadcrumb translations should include localized breadcrumbs for Swedish
✅ Article Template Breadcrumb translations should include localized breadcrumbs for Japanese
✅ Article Template Breadcrumb translations should include localized breadcrumbs for Arabic
✅ Article Template RTL language support should set correct html lang for Arabic
✅ Article Template RTL language support should set correct html lang for Hebrew
✅ Article Template RTL language support should not include dir attribute for LTR languages
✅ Article Template CJK language support should set correct html lang for Japanese
✅ Article Template CJK language support should set correct html lang for Korean
✅ Article Template CJK language support should set correct html lang for Chinese
✅ Article Template Localized date formatting via generateArticleHTML should format date differently for Swedish locale
✅ Article Template Localized date formatting via generateArticleHTML should format date differently for German locale
✅ Article Template Localized date formatting via generateArticleHTML should format date differently for French locale
✅ Article Template Localized source labels should use German source labels
✅ Article Template Localized source labels should use Japanese source labels
✅ Article Template Localized source labels should use Arabic source labels
✅ Article Template Edge cases should generate article with no events
✅ Article Template Edge cases should generate article with no watch points
✅ Article Template Edge cases should generate article with no sources
✅ Article Template Edge cases should use default readTime when not provided
✅ Article Template Edge cases should use default lang when not provided
✅ Article Template Edge cases should handle multiple events across days
✅ Article Template Edge cases should escape HTML in title and subtitle
✅ Article Template All 14 hreflang tags should include hreflang tags for all 14 languages
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale en_US for en
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale sv_SE for sv
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale da_DK for da
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale nb_NO for no
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale fi_FI for fi
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale de_DE for de
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale fr_FR for fr
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale es_ES for es
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale nl_NL for nl
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale ar_SA for ar
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale he_IL for he
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale ja_JP for ja
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale ko_KR for ko
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should output og:locale zh_CN for zh
✅ Article Template og:locale mapping (OG_LOCALE_MAP) should fall back to en_US for unknown language
✅ Article Template Site tagline (SITE_TAGLINE) should include site-tagline div in English
✅ Article Template Site tagline (SITE_TAGLINE) should include Swedish tagline for sv
✅ Article Template Site tagline (SITE_TAGLINE) should include German tagline for de
✅ Article Template Site tagline (SITE_TAGLINE) should include Japanese tagline for ja
✅ Article Template Site tagline (SITE_TAGLINE) should include Arabic tagline for ar
✅ Article Template Site tagline (SITE_TAGLINE) should fall back to English tagline for unknown language
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for en
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for sv
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for de
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for fr
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for ja
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for ar
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for ko
✅ Article Template Watch section titles (WATCH_SECTION_TITLES) should use localized watch title for zh
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for en
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for sv
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for de
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for fr
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for ja
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for ar
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for ko
✅ Article Template Event calendar titles (EVENT_CALENDAR_TITLES) should use localized calendar title for zh
✅ Article Template sanitizeArticleBody in JSON-LD should include sanitized articleBody in JSON-LD
✅ Article Template sanitizeArticleBody in JSON-LD should truncate long articleBody to 500 chars

✅ back-to-top.test.js

✅ Back to Top Button DOM Structure should exist in DOM
✅ Back to Top Button DOM Structure should have back-to-top class
✅ Back to Top Button DOM Structure should have proper aria-label for accessibility
✅ Back to Top Button DOM Structure should have arrow content
✅ Back to Top Button DOM Structure should have id="back-to-top"
✅ Back to Top Button Scroll Visibility should not have visible class initially
✅ Back to Top Button Scroll Visibility should add visible class when pageYOffset > 300
✅ Back to Top Button Scroll Visibility should remove visible class when pageYOffset <= 300
✅ Back to Top Button Scroll Visibility should remove visible class when pageYOffset is 0
✅ Back to Top Button Scroll Visibility should toggle correctly at boundary (300 = hidden, 301 = visible)
✅ Back to Top Button Scroll Visibility should support scroll event listener registration
✅ Back to Top Button Click Behavior should support smooth scrolling API
✅ Back to Top Button Click Behavior should call scrollTo with smooth behavior when no motion preference
✅ Back to Top Button Click Behavior should call scrollTo with auto behavior when prefers-reduced-motion
✅ Back to Top Button Click Behavior should always scroll to top: 0
✅ Back to Top Button Click Behavior should support click event listener registration
✅ Back to Top Button Prefers Reduced Motion should check prefers-reduced-motion media query
✅ Back to Top Button Prefers Reduced Motion should detect when user prefers reduced motion
✅ Back to Top Button Prefers Reduced Motion should use auto behavior for reduced-motion users
✅ Back to Top Button Prefers Reduced Motion should use smooth behavior for standard users
✅ Back to Top Button Edge Cases should handle missing button gracefully
✅ Back to Top Button Edge Cases should handle large scroll values
✅ Back to Top Button Edge Cases should handle negative scroll values

✅ chart-utils.test.js

✅ ChartUtils getResponsiveOptions() should return responsive options for bar chart
✅ ChartUtils getResponsiveOptions() should position legend at top on desktop
✅ ChartUtils getResponsiveOptions() should position legend at bottom on mobile
✅ ChartUtils getResponsiveOptions() should include scales for bar/line/scatter charts
✅ ChartUtils getResponsiveOptions() should not include scales for pie/doughnut charts
✅ ChartUtils getResponsiveOptions() should merge custom options
✅ ChartUtils State Management showLoadingState() should create loading overlay
✅ ChartUtils State Management showEmptyState() should create empty overlay
✅ ChartUtils State Management showErrorState() should create error overlay
✅ ChartUtils State Management hideStateOverlays() should remove all state overlays
✅ ChartUtils State Management should handle non-existent container gracefully
✅ ChartUtils Formatting Utilities formatNumber() should format with Swedish locale
✅ ChartUtils Formatting Utilities formatNumber() should handle decimals
✅ ChartUtils Formatting Utilities formatNumber() should handle null/undefined
✅ ChartUtils Formatting Utilities formatPercent() should format as percentage
✅ ChartUtils Performance Utilities debounce() should delay function execution
✅ ChartUtils Performance Utilities createResizeHandler() should return debounced function
✅ ChartUtils Theme Colors should expose theme colors
✅ ChartUtils Theme Colors should expose party colors
✅ ChartUtils Responsive Breakpoints should expose breakpoint constants
✅ ChartUtils Accessibility addKeyboardNavigation() should add keyboard event listener
✅ ChartUtils Accessibility announceDataPoint() should create live region

✅ coalition-dashboard.test.js

✅ Coalition Dashboard DOM Structure should have coalition dashboard section
✅ Coalition Dashboard DOM Structure should have dashboard-container class
✅ Coalition Dashboard DOM Structure should have all chart canvases
✅ Coalition Dashboard DOM Structure should have D3.js visualization containers
✅ Coalition Dashboard DOM Structure should have wide chart cards
✅ Coalition Dashboard DOM Structure should have data attribution
✅ Coalition Dashboard Accessibility should have ARIA labels on D3 containers
✅ Coalition Dashboard Accessibility should have accessible fallback table for network
✅ Coalition Dashboard Accessibility should have table caption
✅ Coalition Dashboard Accessibility should have proper heading hierarchy
✅ Coalition Dashboard Data Source Configuration should configure local-first URLs for all CSV files
✅ Coalition Dashboard Data Source Configuration should use local paths starting with cia-data/
✅ Coalition Dashboard Data Source Configuration should have remote fallback URLs for all files
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should parse behavioral patterns CSV with real columns
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should parse annual party votes CSV with real columns
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should parse decision trends CSV with real columns
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should parse decision patterns CSV with real columns
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should calculate alignment scores between parties
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should identify coalition blocs
✅ Coalition Dashboard Coalition Data Processing (Real CSV Schema) should aggregate behavioral data by party
✅ Coalition Dashboard D3.js Network should prepare network data nodes for all 8 parties
✅ Coalition Dashboard D3.js Network should prepare network data links
✅ Coalition Dashboard D3.js Network should generate correct number of links for 8 parties
✅ Coalition Dashboard Error Handling and Fallbacks should handle empty CSV data gracefully
✅ Coalition Dashboard Error Handling and Fallbacks should provide fallback coalition data when CSV is empty
✅ Coalition Dashboard Error Handling and Fallbacks should handle fetch failures with mock fallback
✅ Coalition Dashboard Error Handling and Fallbacks should skip aggregate rows with party "-"
✅ Coalition Dashboard Loading State should add loading class to container
✅ Coalition Dashboard Loading State should remove loading class when data loads

✅ coalition-loader.test.js

✅ Coalition Loader CSV Parsing should parse valid CSV with headers and data rows
✅ Coalition Loader CSV Parsing should handle empty CSV
✅ Coalition Loader CSV Parsing should handle CSV with only headers
✅ Coalition Loader CSV Parsing should skip malformed rows with mismatched column count
✅ Coalition Loader CSV Parsing should trim whitespace from values
✅ Coalition Loader CSV Parsing should handle CSV with multiple data rows
✅ Coalition Loader Language Detection should detect English language
✅ Coalition Loader Language Detection should detect Swedish language
✅ Coalition Loader Language Detection should detect Danish language
✅ Coalition Loader Language Detection should detect Norwegian language
✅ Coalition Loader Language Detection should detect German language
✅ Coalition Loader Language Detection should detect French language
✅ Coalition Loader Language Detection should detect Arabic language
✅ Coalition Loader Language Detection should detect Hebrew language
✅ Coalition Loader Language Detection should detect Japanese language
✅ Coalition Loader Language Detection should detect Korean language
✅ Coalition Loader Language Detection should detect Chinese language
✅ Coalition Loader Language Detection should handle language with region code (e.g., en-US)
✅ Coalition Loader Language Detection should handle language with region code (e.g., sv-SE)
✅ Coalition Loader Language Detection should default to empty string when lang not set
✅ Coalition Loader Language Detection should fallback to English for unsupported language
✅ Coalition Loader Translation System should return English translations
✅ Coalition Loader Translation System should return Swedish translations
✅ Coalition Loader Translation System should return Danish translations
✅ Coalition Loader Translation System should fallback to English for unsupported language
✅ Coalition Loader Translation System should fallback to English when language is null
✅ Coalition Loader Translation System should have all required translation keys
✅ Coalition Loader Cache Management should store data with timestamp in cache
✅ Coalition Loader Cache Management should retrieve cached data
✅ Coalition Loader Cache Management should check if cache is fresh (within 7 days)
✅ Coalition Loader Cache Management should detect stale cache (older than 7 days)
✅ Coalition Loader Cache Management should return null for non-existent cache
✅ Coalition Loader Cache Management should handle cache retrieval errors gracefully
✅ Coalition Loader Cache Management should use cache prefix for all keys
✅ Coalition Loader Active Party Filtering should filter parties where active=t
✅ Coalition Loader Active Party Filtering should exclude inactive parties
✅ Coalition Loader Active Party Filtering should return empty array when no active parties
✅ Coalition Loader Active Party Filtering should handle empty party array
✅ Coalition Loader Leader Extraction should prioritize Partiledare over Gruppledare
✅ Coalition Loader Leader Extraction should use Gruppledare when no Partiledare
✅ Coalition Loader Leader Extraction should format leader name as "FirstName LastName"
✅ Coalition Loader Leader Extraction should filter only active leaders (active=t)
✅ Coalition Loader Leader Extraction should handle missing leader data
✅ Coalition Loader Leader Extraction should extract leaders for multiple parties
✅ Coalition Loader Party Sorting should sort parties by parliament seats (descending)
✅ Coalition Loader Party Sorting should handle parties with 0 seats
✅ Coalition Loader Party Sorting should handle missing seat values
✅ Coalition Loader DOM Rendering should find coalition-status container
✅ Coalition Loader DOM Rendering should find cards container
✅ Coalition Loader DOM Rendering should clear existing cards innerHTML
✅ Coalition Loader DOM Rendering should create party card with correct structure
✅ Coalition Loader DOM Rendering should display loading message
✅ Coalition Loader DOM Rendering should display error message
✅ Coalition Loader DOM Rendering should handle missing container gracefully
✅ Coalition Loader DOM Rendering should update coalition status paragraph
✅ Coalition Loader DOM Rendering should render multiple party cards
✅ Coalition Loader Fetch Error Handling should handle HTTP 404 error
✅ Coalition Loader Fetch Error Handling should handle HTTP 500 error
✅ Coalition Loader Fetch Error Handling should handle network timeout
✅ Coalition Loader Fetch Error Handling should implement retry logic
✅ Coalition Loader Fetch Error Handling should handle CORS errors
✅ Coalition Loader Party Metadata should have metadata for all 8 Swedish parties
✅ Coalition Loader Party Metadata should have name for each party
✅ Coalition Loader Party Metadata should have color for each party
✅ Coalition Loader Party Metadata should retrieve party info by code
✅ Coalition Loader Party Metadata should handle unknown party code gracefully
✅ Coalition Loader Integration Scenarios should load data from cache when fresh
✅ Coalition Loader Integration Scenarios should complete full data flow: parse -> filter -> sort -> render
✅ Coalition Loader Integration Scenarios should handle complete error scenario

✅ committees-dashboard.test.js

✅ Committees Dashboard DOM Structure should have committee dashboard section
✅ Committees Dashboard DOM Structure should have dashboard-container class
✅ Committees Dashboard DOM Structure should have all chart canvases
✅ Committees Dashboard DOM Structure should have D3 visualization containers
✅ Committees Dashboard DOM Structure should have wide chart cards
✅ Committees Dashboard DOM Structure should have last updated timestamp
✅ Committees Dashboard Accessibility should have ARIA labels on D3 containers
✅ Committees Dashboard Accessibility should have accessible fallback tables
✅ Committees Dashboard Accessibility should have table captions
✅ Committees Dashboard Accessibility should have proper heading hierarchy
✅ Committees Dashboard Committee Data Processing should parse committee productivity matrix CSV with real columns
✅ Committees Dashboard Committee Data Processing should parse committee ballot decision summary CSV with real columns
✅ Committees Dashboard Committee Data Processing should rank committees by effectiveness
✅ Committees Dashboard Committee Data Processing should calculate productivity metrics
✅ Committees Dashboard Data Source Configuration should use local-first URLs with cia-data/ prefix
✅ Committees Dashboard Data Source Configuration should have remote fallback URLs
✅ Committees Dashboard Error Handling should handle empty CSV data
✅ Committees Dashboard Error Handling should handle fetch failures gracefully
✅ Committees Dashboard Chart Configuration should create comparison bar chart
✅ Committees Dashboard Data Attribution should have data attribution section
✅ Committees Dashboard Data Attribution should reference CIA Platform as data source

✅ csv-validation.test.js

✅ CIA CSV Data Validation File Existence should have distribution_politician_risk_levels.csv
✅ CIA CSV Data Validation File Existence should have distribution_risk_by_party.csv
✅ CIA CSV Data Validation File Existence should have distribution_risk_evolution_temporal.csv
✅ CIA CSV Data Validation File Existence should have distribution_crisis_resilience.csv
✅ CIA CSV Data Validation File Existence should have percentile_voting_anomaly_detection.csv
✅ CIA CSV Data Validation File Existence should have distribution_party_effectiveness_trends.csv
✅ CIA CSV Data Validation File Existence should have distribution_party_momentum.csv
✅ CIA CSV Data Validation File Existence should have distribution_annual_committee_documents.csv
✅ CIA CSV Data Validation File Existence should have distribution_committee_productivity_matrix.csv
✅ CIA CSV Data Validation File Existence should have distribution_ministry_effectiveness.csv
✅ CIA CSV Data Validation File Existence should have distribution_ministry_decision_impact.csv
✅ CIA CSV Data Validation File Existence should have distribution_ministry_productivity_matrix.csv
✅ CIA CSV Data Validation File Existence should have distribution_ministry_risk_levels.csv
✅ CIA CSV Data Validation File Existence should have distribution_ministry_risk_quarterly.csv
✅ CIA CSV Data Validation File Existence should have distribution_person_status.csv
✅ CIA CSV Data Validation File Existence should have distribution_experience_levels.csv
✅ CIA CSV Data Validation File Existence should have distribution_experience_by_party.csv
✅ CIA CSV Data Validation File Existence should have extraction_summary_report.csv
✅ CIA CSV Data Validation File Size Validation distribution_politician_risk_levels.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_risk_by_party.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_risk_evolution_temporal.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_crisis_resilience.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation percentile_voting_anomaly_detection.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_party_effectiveness_trends.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_party_momentum.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_annual_committee_documents.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_committee_productivity_matrix.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_ministry_effectiveness.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_ministry_decision_impact.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_ministry_productivity_matrix.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_ministry_risk_levels.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_ministry_risk_quarterly.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_person_status.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_experience_levels.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation distribution_experience_by_party.csv should not be empty or too small
✅ CIA CSV Data Validation File Size Validation extraction_summary_report.csv should not be empty or too small
✅ CIA CSV Data Validation Encoding Validation distribution_politician_risk_levels.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_risk_by_party.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_risk_evolution_temporal.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_crisis_resilience.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation percentile_voting_anomaly_detection.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_party_effectiveness_trends.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_party_momentum.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_annual_committee_documents.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_committee_productivity_matrix.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_ministry_effectiveness.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_ministry_decision_impact.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_ministry_productivity_matrix.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_ministry_risk_levels.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_ministry_risk_quarterly.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_person_status.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_experience_levels.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation distribution_experience_by_party.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation Encoding Validation extraction_summary_report.csv should have valid UTF-8 encoding
✅ CIA CSV Data Validation CSV Structure Validation distribution_politician_risk_levels.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_politician_risk_levels.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_risk_by_party.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_risk_by_party.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_risk_evolution_temporal.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_risk_evolution_temporal.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_crisis_resilience.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_crisis_resilience.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation percentile_voting_anomaly_detection.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation percentile_voting_anomaly_detection.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_party_effectiveness_trends.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_party_effectiveness_trends.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_party_momentum.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_party_momentum.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_annual_committee_documents.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_annual_committee_documents.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_committee_productivity_matrix.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_committee_productivity_matrix.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_effectiveness.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_effectiveness.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_decision_impact.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_decision_impact.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_productivity_matrix.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_productivity_matrix.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_risk_levels.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_risk_levels.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_risk_quarterly.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_ministry_risk_quarterly.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_person_status.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_person_status.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_experience_levels.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_experience_levels.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation distribution_experience_by_party.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation distribution_experience_by_party.csv should have data rows
✅ CIA CSV Data Validation CSV Structure Validation extraction_summary_report.csv should have proper CSV structure
✅ CIA CSV Data Validation CSV Structure Validation extraction_summary_report.csv should have data rows
✅ CIA CSV Data Validation Schema Validation distribution_politician_risk_levels.csv should exist and be parseable
✅ CIA CSV Data Validation Schema Validation distribution_politician_risk_levels.csv should have required columns
✅ CIA CSV Data Validation Schema Validation distribution_politician_risk_levels.csv should have valid numeric data types
✅ CIA CSV Data Validation Schema Validation distribution_risk_by_party.csv should exist and be parseable
✅ CIA CSV Data Validation Schema Validation distribution_risk_by_party.csv should have required columns
✅ CIA CSV Data Validation Schema Validation distribution_risk_by_party.csv should have valid numeric data types
✅ CIA CSV Data Validation Schema Validation distribution_party_effectiveness_trends.csv should exist and be parseable
✅ CIA CSV Data Validation Schema Validation distribution_party_effectiveness_trends.csv should have required columns
✅ CIA CSV Data Validation Schema Validation distribution_party_effectiveness_trends.csv should have valid numeric data types
✅ CIA CSV Data Validation Schema Validation distribution_ministry_effectiveness.csv should exist and be parseable
✅ CIA CSV Data Validation Schema Validation distribution_ministry_effectiveness.csv should have required columns
✅ CIA CSV Data Validation Schema Validation distribution_ministry_effectiveness.csv should have valid numeric data types
✅ CIA CSV Data Validation Schema Validation distribution_committee_productivity_matrix.csv should exist and be parseable
✅ CIA CSV Data Validation Schema Validation distribution_committee_productivity_matrix.csv should have required columns
✅ CIA CSV Data Validation Schema Validation distribution_committee_productivity_matrix.csv should have valid numeric data types
✅ CIA CSV Data Validation Column Consistency distribution_politician_risk_levels.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_risk_by_party.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_risk_evolution_temporal.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_crisis_resilience.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency percentile_voting_anomaly_detection.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_party_effectiveness_trends.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_party_momentum.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_annual_committee_documents.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_committee_productivity_matrix.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_ministry_effectiveness.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_ministry_decision_impact.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_ministry_productivity_matrix.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_ministry_risk_levels.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_ministry_risk_quarterly.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_person_status.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_experience_levels.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency distribution_experience_by_party.csv should have consistent column counts
✅ CIA CSV Data Validation Column Consistency extraction_summary_report.csv should have consistent column counts
✅ CIA CSV Data Validation Data Freshness CSV files should not be older than 90 days (warns at 30 days)

✅ data-transformers.test.js

✅ Data Transformers transformCalendarToEventGrid should transform events to grid structure for English
✅ Data Transformers transformCalendarToEventGrid should transform events to grid structure for Swedish
✅ Data Transformers transformCalendarToEventGrid should handle empty events array
✅ Data Transformers transformCalendarToEventGrid should handle null/undefined events
✅ Data Transformers transformCalendarToEventGrid should support all 14 languages via Intl formatting
✅ Data Transformers transformCalendarToEventGrid should handle events with different date field names
✅ Data Transformers transformCalendarToEventGrid should group events by date
✅ Data Transformers generateArticleContent should generate HTML content for week-ahead article
✅ Data Transformers generateArticleContent should generate content in Swedish
✅ Data Transformers generateArticleContent should support different article types
✅ Data Transformers extractWatchPoints should extract watch points from events
✅ Data Transformers extractWatchPoints should extract watch points in Swedish
✅ Data Transformers extractWatchPoints should handle empty data
✅ Data Transformers extractTopics should extract topics from events
✅ Data Transformers extractTopics should return unique topics
✅ Data Transformers generateMetadata should generate metadata with keywords, topics, tags
✅ Data Transformers generateMetadata should generate Swedish metadata
✅ Data Transformers calculateReadTime should calculate read time for short content
✅ Data Transformers calculateReadTime should calculate read time for long content
✅ Data Transformers calculateReadTime should handle empty content
✅ Data Transformers calculateReadTime should handle content with only HTML tags
✅ Data Transformers calculateReadTime should never return less than 1 minute
✅ Data Transformers generateArticleContent edge cases should handle unknown article type gracefully
✅ Data Transformers generateArticleContent edge cases should handle committee-reports with empty reports array
✅ Data Transformers generateArticleContent edge cases should handle propositions with data
✅ Data Transformers generateArticleContent edge cases should handle motions with data
✅ Data Transformers generateArticleContent edge cases should include highlights section when highlights are provided
✅ Data Transformers generateArticleContent edge cases should include Swedish highlights section
✅ Data Transformers generateArticleContent edge cases should handle events with no date field
✅ Data Transformers generateSources should generate sources list from MCP tools
✅ Data Transformers generateSources should handle empty tools array
✅ Data Transformers generateSources should include descriptive source names
✅ Data Transformers generateSources should include sources for all MCP tool types
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) should have labels for all 14 supported languages
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) should have all required keys in every language
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) should have non-empty string values for static labels
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) should have function values for Desc labels
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) L() helper should return correct label for known language
✅ Data Transformers Multi-language content labels (CONTENT_LABELS) L() helper should fallback to English for unknown language
✅ Data Transformers Multi-language article content generation should generate localized content for all 14 languages
✅ Data Transformers Multi-language article content generation should generate localized committee content for German
✅ Data Transformers Multi-language article content generation should generate localized propositions content for French
✅ Data Transformers Multi-language article content generation should generate localized motions content for Japanese
✅ Data Transformers Multi-language article content generation should generate localized metadata tags
✅ Data Transformers data-translate markers for Swedish API content should wrap Swedish titel in data-translate span for committee reports
✅ Data Transformers data-translate markers for Swedish API content should NOT wrap English title in data-translate span for committee reports
✅ Data Transformers data-translate markers for Swedish API content should wrap Swedish titel in data-translate span for propositions
✅ Data Transformers data-translate markers for Swedish API content should NOT wrap English title in data-translate span for propositions
✅ Data Transformers data-translate markers for Swedish API content should wrap Swedish titel in data-translate span for motions
✅ Data Transformers data-translate markers for Swedish API content should NOT wrap English title in data-translate span for motions
✅ Data Transformers data-translate markers for Swedish API content should wrap Swedish summary in data-translate span when present
✅ Data Transformers data-translate markers for Swedish API content should use localized default or enhanced summary when no API summary provided
✅ Data Transformers data-translate markers for Swedish API content should wrap week-ahead event titel in data-translate span
✅ Data Transformers data-translate markers for Swedish API content should NOT wrap week-ahead event with English title
✅ Data Transformers HTML escaping in data-translate spans (XSS prevention) should escape HTML special characters in Swedish titles
✅ Data Transformers HTML escaping in data-translate spans (XSS prevention) should escape HTML in Swedish summaries
✅ Data Transformers HTML escaping in data-translate spans (XSS prevention) should escape HTML in document names
✅ Data Transformers dokumentnamn fallback chain should use dokumentnamn as link text when available
✅ Data Transformers dokumentnamn fallback chain should fall back to dok_id when dokumentnamn missing
✅ Data Transformers dokumentnamn fallback chain should fall back to title text when both dokumentnamn and dok_id missing
✅ Data Transformers dokumentnamn fallback chain should never render "undefined" as link text
✅ Data Transformers dokumentnamn fallback chain should apply dokumentnamn fallback for propositions
✅ Data Transformers dokumentnamn fallback chain should apply dokumentnamn fallback for motions
✅ Data Transformers extractWatchPoints with data-translate markers should wrap Swedish event titles in data-translate span
✅ Data Transformers extractWatchPoints with data-translate markers should NOT wrap English event titles in data-translate span
✅ Data Transformers extractWatchPoints with data-translate markers should escape HTML in watch point titles

✅ editorial-pillars.test.js

✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have all 14 supported languages
✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have all 4 pillar headings for each language
✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have non-empty strings for all headings
✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have unique headings per language (no duplicates)
✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have correct English headings
✅ editorial-pillars EDITORIAL_PILLAR_HEADINGS should have correct Swedish headings
✅ editorial-pillars detectArticleLanguage should detect English from HTML lang attribute
✅ editorial-pillars detectArticleLanguage should detect Swedish from HTML lang attribute
✅ editorial-pillars detectArticleLanguage should detect language with case-insensitive matching
✅ editorial-pillars detectArticleLanguage should detect language with extra attributes
✅ editorial-pillars detectArticleLanguage should fallback to English when lang attribute is missing
✅ editorial-pillars detectArticleLanguage should fallback to English when lang is unsupported
✅ editorial-pillars detectArticleLanguage should fallback to English for empty HTML
✅ editorial-pillars detectArticleLanguage should fallback to English for null input
✅ editorial-pillars detectArticleLanguage should fallback to English for malformed HTML
✅ editorial-pillars detectArticleLanguage should detect all 14 supported languages
✅ editorial-pillars detectArticleLanguage should extract first lang attribute when multiple html tags
✅ editorial-pillars getLocalizedHeading should return correct heading for English
✅ editorial-pillars getLocalizedHeading should return correct heading for Swedish
✅ editorial-pillars getLocalizedHeading should return correct heading for Norwegian
✅ editorial-pillars getLocalizedHeading should return correct heading for Arabic (RTL)
✅ editorial-pillars getLocalizedHeading should return correct heading for Hebrew (RTL)
✅ editorial-pillars getLocalizedHeading should return correct heading for Japanese
✅ editorial-pillars getLocalizedHeading should fallback to English for unsupported language
✅ editorial-pillars getLocalizedHeading should fallback to English for null language
✅ editorial-pillars getLocalizedHeading should fallback to English for undefined language
✅ editorial-pillars getLocalizedHeading should handle all pillars for all 14 languages
✅ editorial-pillars getLocalizedHeading should return undefined for non-existent pillar
✅ editorial-pillars Integration should work together: detect language and get localized heading
✅ editorial-pillars Integration should work with fallback chain: unknown lang -> English heading

✅ extract-vocabulary.test.js

✅ extract-vocabulary.js Language code extraction should extract language code from filename
✅ extract-vocabulary.js Language code extraction should handle multiple language files
✅ extract-vocabulary.js Structure-based extraction should extract committee label from strong tag
✅ extract-vocabulary.js Structure-based extraction should extract labels in multiple languages
✅ extract-vocabulary.js Structure-based extraction should extract What to Watch heading
✅ extract-vocabulary.js Structure-based extraction should extract h3 titles with nested span tags
✅ extract-vocabulary.js CLI arguments should filter by date prefix
✅ extract-vocabulary.js CLI arguments should show help message
✅ extract-vocabulary.js Error handling should report skipped files with reasons
✅ extract-vocabulary.js Error handling should handle read errors gracefully
✅ extract-vocabulary.js Article type detection should detect committee reports
✅ extract-vocabulary.js Article type detection should detect multiple article types

✅ generate-news-enhanced-part1.test.js

✅ Generate News Enhanced - Part 1 Module Constants should export VALID_ARTICLE_TYPES with all supported types
✅ Generate News Enhanced - Part 1 Module Constants should export ALL_LANGUAGES with all 14 supported languages
✅ Generate News Enhanced - Part 1 Module Constants should export LANGUAGE_PRESETS with all preset categories
✅ Generate News Enhanced - Part 1 Module Constants nordic preset should include Nordic languages
✅ Generate News Enhanced - Part 1 Module Constants eu-core preset should include EU core languages
✅ Generate News Enhanced - Part 1 Module Constants all preset should include all 14 languages
✅ Generate News Enhanced - Part 1 formatDateForSlug should be an exported function
✅ Generate News Enhanced - Part 1 formatDateForSlug should format date correctly
✅ Generate News Enhanced - Part 1 formatDateForSlug should pad single-digit months and days
✅ Generate News Enhanced - Part 1 formatDateForSlug should use current date when called with no arguments
✅ Generate News Enhanced - Part 1 getWeekAheadDateRange should be an exported function
✅ Generate News Enhanced - Part 1 getWeekAheadDateRange should return object with start and end dates
✅ Generate News Enhanced - Part 1 getWeekAheadDateRange should return dates in ISO format
✅ Generate News Enhanced - Part 1 getWeekAheadDateRange should return a 7-day range
✅ Generate News Enhanced - Part 1 getWeekAheadDateRange end date should be after start date
✅ Generate News Enhanced - Part 1 writeSingleArticle should be an exported function
✅ Generate News Enhanced - Part 1 writeSingleArticle should accept html, slug, and language parameters
✅ Generate News Enhanced - Part 1 writeSingleArticle should return filename
✅ Generate News Enhanced - Part 1 writeSingleArticle should call fs.writeFileSync
✅ Generate News Enhanced - Part 1 writeSingleArticle should include language in filename
✅ Generate News Enhanced - Part 1 writeArticlePair should be an exported function
✅ Generate News Enhanced - Part 1 writeArticlePair should write both English and Swedish versions
✅ Generate News Enhanced - Part 1 generateWeekAhead should be an exported function
✅ Generate News Enhanced - Part 1 generateWeekAhead should return result with success status
✅ Generate News Enhanced - Part 1 generateWeekAhead should generate files for requested languages
✅ Generate News Enhanced - Part 1 generateWeekAhead should include date in slug
✅ Generate News Enhanced - Part 1 generateWeekAhead should call MCP client fetchCalendarEvents
✅ Generate News Enhanced - Part 1 generateWeekAhead should handle MCP client errors gracefully

✅ generate-news-enhanced-part2.test.js

✅ Generate News Enhanced - Part 2 generateCommitteeReports should be an exported function
✅ Generate News Enhanced - Part 2 generateCommitteeReports should return result with success status
✅ Generate News Enhanced - Part 2 generateCommitteeReports should call MCP client fetchCommitteeReports
✅ Generate News Enhanced - Part 2 generateCommitteeReports should handle empty results
✅ Generate News Enhanced - Part 2 generateCommitteeReports should handle MCP client errors gracefully
✅ Generate News Enhanced - Part 2 generateCommitteeReports should include committee-reports in slug
✅ Generate News Enhanced - Part 2 generatePropositions should be an exported function
✅ Generate News Enhanced - Part 2 generatePropositions should return result with success status
✅ Generate News Enhanced - Part 2 generatePropositions should call MCP client fetchPropositions
✅ Generate News Enhanced - Part 2 generatePropositions should handle empty results
✅ Generate News Enhanced - Part 2 generatePropositions should handle MCP client errors gracefully
✅ Generate News Enhanced - Part 2 generatePropositions should include government-propositions in slug
✅ Generate News Enhanced - Part 2 generateMotions should be an exported function
✅ Generate News Enhanced - Part 2 generateMotions should return result with success status
✅ Generate News Enhanced - Part 2 generateMotions should call MCP client fetchMotions
✅ Generate News Enhanced - Part 2 generateMotions should handle empty results
✅ Generate News Enhanced - Part 2 generateMotions should handle MCP client errors gracefully
✅ Generate News Enhanced - Part 2 generateMotions should include opposition-motions in slug
✅ Generate News Enhanced - Part 2 generateNews should be an exported function
✅ Generate News Enhanced - Part 2 generateNews should return stats object
✅ Generate News Enhanced - Part 2 generateNews should generate articles and update stats
✅ Generate News Enhanced - Part 2 generateNews should write metadata files
✅ Generate News Enhanced - Part 2 Article Type Validation should include all documented article types
✅ Generate News Enhanced - Part 2 Language Preset Coverage nordic preset should cover Scandinavian+Finnish languages
✅ Generate News Enhanced - Part 2 Language Preset Coverage eu-core preset should cover major EU languages
✅ Generate News Enhanced - Part 2 Language Preset Coverage all preset should cover all 14 languages including CJK and RTL
✅ Generate News Enhanced - Part 2 News Directory Structure should have news directory
✅ Generate News Enhanced - Part 2 Week Ahead Title Translations should have title translations for all 14 languages
✅ Generate News Enhanced - Part 2 Week Ahead Title Translations title languages should match ALL_LANGUAGES constant
✅ MCP Client Integration should be able to import MCPClient
✅ Data Transformer Integration should be able to import all required transformers
✅ Article Template Integration should be able to import generateArticleHTML

✅ generate-news-indexes.test.js

✅ Generate News Indexes parseArticleMetadata should parse metadata from a real article file
✅ Generate News Indexes parseArticleMetadata should return null for non-article files
✅ Generate News Indexes parseArticleMetadata should extract correct language from filename suffix
✅ Generate News Indexes parseArticleMetadata should classify week-ahead articles as prospective
✅ Generate News Indexes parseArticleMetadata should classify committee-reports as analysis
✅ Generate News Indexes parseArticleMetadata should extract topics from article:tag meta tags
✅ Generate News Indexes parseArticleMetadata should extract tags from article:tag meta tags
✅ Generate News Indexes scanNewsArticles should return object with all 14 language keys
✅ Generate News Indexes scanNewsArticles should return arrays for each language
✅ Generate News Indexes scanNewsArticles should sort articles by date descending
✅ Generate News Indexes generateAllIndexes should return result object with success status
✅ Generate News Indexes generateAllIndexes should generate indexes successfully
✅ Generate News Indexes generateAllIndexes should generate index files for all 14 languages
✅ Generate News Indexes generateAllIndexes should generate index files with correct lang attribute
✅ Generate News Indexes generateAllIndexes should include domain-specific keywords in generated indexes
✅ Generate News Indexes generateAllIndexes should include translated Schema.org WebSite description per language
✅ Generate News Indexes generateAllIndexes should include publisher and about in Schema.org ItemList articles
✅ Generate News Indexes generateAllIndexes should set dir="rtl" for Arabic and Hebrew indexes
✅ Generate News Indexes classifyArticleType multi-language should classify German prospective articles
✅ Generate News Indexes classifyArticleType multi-language should classify French analysis articles
✅ Generate News Indexes classifyArticleType multi-language should classify Japanese breaking news articles
✅ Generate News Indexes classifyArticleType multi-language should classify Arabic prospective articles
✅ Generate News Indexes classifyArticleType multi-language should classify Finnish analysis articles
✅ Generate News Indexes classifyArticleType multi-language should classify Korean breaking news articles
✅ Generate News Indexes classifyArticleType multi-language should default to retrospective when no keywords match
✅ Generate News Indexes extractTopics multi-language should extract topics from German tags
✅ Generate News Indexes extractTopics multi-language should extract topics from Japanese tags
✅ Generate News Indexes extractTopics multi-language should extract topics from Arabic tags

✅ generate-sitemap.test.js

✅ Sitemap Generation generateSitemap should return valid XML string
✅ Sitemap Generation generateSitemap should include main index page
✅ Sitemap Generation generateSitemap should include language index pages
✅ Sitemap Generation generateSitemap should include politician dashboard page
✅ Sitemap Generation generateSitemap should include dashboard pages
✅ Sitemap Generation generateSitemap should include sitemap HTML pages
✅ Sitemap Generation generateSitemap should include xhtml namespace for hreflang
✅ Sitemap Generation generateSitemap should include hreflang alternate links
✅ Sitemap Generation generateSitemap should include changefreq and priority tags
✅ Sitemap Generation generateSitemap should include lastmod tags
✅ Sitemap Generation generateSitemap should include news index pages
✅ Sitemap Generation validateSitemap should pass for valid sitemap XML
✅ Sitemap Generation validateSitemap should return true for valid sitemap
✅ Sitemap Generation validateSitemap should throw for missing XML declaration
✅ Sitemap Generation validateSitemap should throw for missing sitemap namespace
✅ Sitemap Generation validateSitemap should throw for empty sitemap with no URLs
✅ Sitemap Generation validateSitemap should throw for sitemap with no <loc> tags

✅ html-utils.test.js

✅ html-utils escapeHtml should escape ampersands
✅ html-utils escapeHtml should escape angle brackets
✅ html-utils escapeHtml should escape double quotes
✅ html-utils escapeHtml should escape single quotes
✅ html-utils escapeHtml should handle null input
✅ html-utils escapeHtml should handle undefined input
✅ html-utils escapeHtml should handle empty string
✅ html-utils escapeHtml should handle numeric input via String coercion
✅ html-utils escapeHtml should handle strings with no special characters
✅ html-utils escapeHtml should escape all special characters together

✅ jsdoc-validation.test.js

✅ JSDoc Generation & Validation JSDoc Build Process should generate JSDoc without errors
✅ JSDoc Generation & Validation JSDoc Build Process should create api/ directory
✅ JSDoc Generation & Validation JSDoc Build Process should generate index.html in api/
✅ JSDoc Generation & Validation Generated Documentation Structure should generate HTML files for each module
✅ JSDoc Generation & Validation Generated Documentation Structure should create module documentation files
✅ JSDoc Generation & Validation Generated Documentation Structure should generate global.html for global functions
✅ JSDoc Generation & Validation Documentation Content Validation should contain intelligence operative terminology in index.html
✅ JSDoc Generation & Validation Documentation Content Validation should reference CIA Platform in documentation
✅ JSDoc Generation & Validation Documentation Content Validation should include political transparency mission
✅ JSDoc Generation & Validation Documentation Content Validation should document GDPR compliance for political data
✅ JSDoc Generation & Validation Source Code JSDoc Coverage should have JSDoc comments in stats-loader.js
✅ JSDoc Generation & Validation Source Code JSDoc Coverage should have JSDoc comments in risk-dashboard.js
✅ JSDoc Generation & Validation Source Code JSDoc Coverage should document functions with @param and @returns tags
✅ JSDoc Generation & Validation Documentation Accessibility should generate valid HTML structure
✅ JSDoc Generation & Validation Documentation Accessibility should include navigation elements for accessibility
✅ JSDoc Generation & Validation Documentation Accessibility should have proper document title
✅ JSDoc Generation & Validation Integration with Project Documentation should reference ARCHITECTURE.md
✅ JSDoc Generation & Validation Integration with Project Documentation should reference THREAT_MODEL.md for security context
✅ JSDoc Generation & Validation Integration with Project Documentation should link to GitHub repository
✅ JSDoc File Completeness should list all expected JavaScript source directories
✅ JSDoc File Completeness should document all dashboard JavaScript files

✅ load-cia-stats.test.js

✅ Load CIA Stats Script Script Configuration should have load-cia-stats.js script
✅ Load CIA Stats Script Script Configuration should be a Node.js ES module
✅ Load CIA Stats Script CIA Data Source should reference extraction_summary_report.csv
✅ Load CIA Stats Script CIA Data Source should fetch from GitHub cia repository
✅ Load CIA Stats Script ISMS Compliance Documentation should include ISO 27001 compliance comments
✅ Load CIA Stats Script ISMS Compliance Documentation should document data classification
✅ Load CIA Stats Script ISMS Compliance Documentation should reference GDPR compliance
✅ Load CIA Stats Script ISMS Compliance Documentation should reference Swedish Offentlighetsprincipen
✅ Load CIA Stats Script Statistics Extraction should extract total_persons statistic
✅ Load CIA Stats Script Statistics Extraction should extract total_votes statistic
✅ Load CIA Stats Script Statistics Extraction should extract total_documents statistic
✅ Load CIA Stats Script Statistics Extraction should extract total_committee_documents statistic
✅ Load CIA Stats Script Statistics Extraction should extract total_rule_violations statistic
✅ Load CIA Stats Script Output Generation should output to cia-data/production-stats.json
✅ Load CIA Stats Script Output Generation should create JSON output with proper structure
✅ Load CIA Stats Script Caching Strategy should implement cache freshness check
✅ Load CIA Stats Script Caching Strategy should include last_updated timestamp
✅ Load CIA Stats Script Error Handling should have error handling for network failures
✅ Load CIA Stats Script Error Handling should have try-catch blocks
✅ Load CIA Stats Script CSV Parsing should parse CSV content
✅ Load CIA Stats Script CSV Parsing should handle CSV headers
✅ Load CIA Stats Script Data Validation should validate extracted statistics are numbers
✅ Load CIA Stats Script Data Validation should have reasonable statistic values (sanity check)
✅ Load CIA Stats Script Integration with Update Script should be compatible with update-stats-from-cia.js
✅ Load CIA Stats Script GitHub Actions Integration should be referenced in update-cia-stats workflow
✅ Load CIA Stats Script GitHub Actions Integration should have scheduled workflow for daily updates

✅ mcp-client-core-part1.test.js

✅ MCPClient constructor should create client with default configuration
✅ MCPClient constructor should accept custom configuration
✅ MCPClient constructor should accept string URL for backwards compatibility
✅ MCPClient constructor should accept serverUrl alias in config
✅ MCPClient constructor should initialize request and error counts to zero
✅ MCPClient constructor should accept custom headers in config
✅ MCPClient constructor should initialize empty customHeaders when no headers provided
✅ MCPClient constructor should initialize empty customHeaders for string URL config
✅ MCPClient request should make successful HTTP request with JSON-RPC 2.0
✅ MCPClient request should send correct JSON-RPC 2.0 request format
✅ MCPClient request should include custom headers from config in requests
✅ MCPClient request should not override runtime headers with custom headers
✅ MCPClient request should handle JSON-RPC error responses
✅ MCPClient request should throw on non-ok HTTP response
✅ MCPClient request should throw on 404 response
✅ MCPClient request should retry on network error
✅ MCPClient request should retry on ECONNREFUSED error
✅ MCPClient request should fail after max retries
✅ MCPClient request should not retry on non-network errors
✅ MCPClient request should track statistics
✅ MCPClient request should use default empty params when none provided
✅ MCPClient request should not add prefix when using direct server URL
✅ MCPClient request should add prefix when using MCP gateway URL
✅ MCPClient request should try without prefix if gateway returns Internal error
✅ MCPClient sleep should resolve after specified delay
✅ MCPClient fetchCalendarEvents should fetch calendar events with date range
✅ MCPClient fetchCalendarEvents should pass optional org and akt parameters
✅ MCPClient fetchCalendarEvents should return empty array when response has no events key
✅ MCPClient fetchCommitteeReports should fetch committee reports with limit
✅ MCPClient fetchCommitteeReports should pass optional rm and organ parameters
✅ MCPClient fetchCommitteeReports should return empty array when response has no reports key
✅ MCPClient fetchPropositions should fetch propositions with default limit
✅ MCPClient fetchPropositions should pass optional rm parameter
✅ MCPClient fetchPropositions should call correct tool name
✅ MCPClient fetchPropositions should return empty array when response has no propositions key

✅ mcp-client-core-part2.test.js

✅ MCPClient Part 2 fetchMotions should fetch motions with default limit
✅ MCPClient Part 2 fetchMotions should pass optional rm parameter
✅ MCPClient Part 2 fetchMotions should call correct tool name
✅ MCPClient Part 2 fetchMotions should return empty array when response has no motions key
✅ MCPClient Part 2 searchDocuments should search documents with query parameters
✅ MCPClient Part 2 searchDocuments should call correct tool name
✅ MCPClient Part 2 searchDocuments should return empty array when response has no documents key
✅ MCPClient Part 2 searchSpeeches should search speeches with query parameters
✅ MCPClient Part 2 searchSpeeches should call correct tool name
✅ MCPClient Part 2 searchSpeeches should return empty array when response has no speeches key
✅ MCPClient Part 2 fetchMPs should fetch MPs with filters
✅ MCPClient Part 2 fetchMPs should call correct tool name
✅ MCPClient Part 2 fetchMPs should pass empty object when no filters provided
✅ MCPClient Part 2 fetchMPs should return empty array when response has no mps key
✅ MCPClient Part 2 fetchVotingRecords should fetch voting records with filters
✅ MCPClient Part 2 fetchVotingRecords should call correct tool name
✅ MCPClient Part 2 fetchVotingRecords should return empty array when response has no votes key
✅ MCPClient Part 2 fetchGovernmentDocuments should fetch government documents
✅ MCPClient Part 2 fetchGovernmentDocuments should call correct tool name
✅ MCPClient Part 2 fetchGovernmentDocuments should return empty array when response has no documents key
✅ MCPClient Part 2 getStats should return request statistics
✅ MCPClient Part 2 getStats should return 0% success rate when no requests made
✅ MCPClient Part 2 getStats should calculate success rate correctly
✅ MCPClient Part 2 getStats should show 100% success rate when all requests succeed
✅ MCPClient Part 2 resetStats should reset request and error counts to zero
✅ MCPClient Part 2 resetStats should reset after errors too
✅ MCPClient Part 2 tool name validation should reject empty tool names
✅ MCPClient Part 2 tool name validation should reject null/undefined tool names
✅ MCPClient Part 2 tool name validation should reject non-string tool names
✅ MCPClient Part 2 tool name validation should reject tool names with path traversal characters
✅ MCPClient Part 2 tool name validation should reject tool names with special characters
✅ MCPClient Part 2 tool name validation should accept valid tool names
✅ MCPClient Part 2 error counting accuracy should not over-count errors on retried requests
✅ MCPClient Part 2 error counting accuracy should count exactly one error for a fully failed request

✅ mcp-client-exports.test.js

✅ Module convenience exports should export getDefaultClient function
✅ Module convenience exports should return MCPClient instance from getDefaultClient
✅ Module convenience exports should return same instance on repeated getDefaultClient calls
✅ Module convenience exports should export all convenience functions
✅ Module convenience exports convenience fetchCalendarEvents should delegate to default client
✅ Module convenience exports convenience fetchPropositions should delegate to default client
✅ Module convenience exports convenience searchDocuments should delegate to default client
✅ Module convenience exports convenience fetchMPs should delegate to default client
✅ Module convenience exports convenience fetchMotions should delegate to default client
✅ Module convenience exports convenience searchSpeeches should delegate to default client
✅ Module convenience exports convenience fetchVotingRecords should delegate to default client
✅ Module convenience exports convenience fetchGovernmentDocuments should delegate to default client
✅ Module convenience exports convenience fetchCommitteeReports should delegate to default client

✅ news-article-generator-integration.test.js

✅ News Article Generator Integration Cross-Reference Validation should validate week-ahead cross-references
✅ News Article Generator Integration Cross-Reference Validation should validate committee-reports cross-references
✅ News Article Generator Integration Cross-Reference Validation should detect missing required tools
✅ News Article Generator Integration Cross-Reference Validation should track extra tools used
✅ News Article Generator Integration Required Tools Configuration should define required tools for all article types
✅ News Article Generator Integration Required Tools Configuration should require minimum 3 sources per article type
✅ News Article Generator Integration Cross-Reference Patterns should extract calendar references from content
✅ News Article Generator Integration Cross-Reference Patterns should extract document references from content
✅ News Article Generator Integration Cross-Reference Patterns should extract vote references from content
✅ News Article Generator Integration Cross-Reference Patterns should extract multiple reference types
✅ News Article Generator Integration Batch Validation should validate multiple articles at once
✅ News Article Generator Integration Batch Validation should calculate average score
✅ News Article Generator Integration Validation Reporting should generate markdown validation report
✅ News Article Generator Integration Validation Reporting should export CI-friendly summary
✅ News Article Generator Integration Validation Reporting should mark success when all articles pass
✅ News Article Generator Integration Quality Score Calculation should score perfect articles highly
✅ News Article Generator Integration Quality Score Calculation should score incomplete articles lower

✅ news-evening-analysis.test.js

✅ Evening Analysis Structure Validation should parse evening analysis articles correctly
✅ Evening Analysis Structure Validation should include all 5 Editorial Pillars
✅ Evening Analysis Structure Validation should have minimum 200 words per major section
✅ Evening Analysis Structure Validation should have analytical thesis in lead paragraph
✅ Evening Analysis Structure Validation should validate proper HTML structure
✅ Evening Analysis Structure Validation should have proper hreflang tags for all languages
✅ Evening Analysis Structure Validation should include Schema.org NewsArticle structured data
✅ Evening Analysis Structure Validation should use external styles.css instead of embedded CSS
✅ Evening Analysis Structure Validation should follow Economist-style journalism standards
✅ Evening Analysis Structure Validation should have RTL direction for Arabic articles
✅ Analytical Depth Tests should include historical context
✅ Analytical Depth Tests should have international comparison when appropriate
✅ Analytical Depth Tests should include "so what" analysis
✅ Analytical Depth Tests should include "what next" analysis
✅ Analytical Depth Tests should calculate analytical depth score
✅ Analytical Depth Tests should include multiple party perspectives
✅ Analytical Depth Tests should cite riksdag-regering-mcp sources
✅ Cross-Workflow Coordination Tests should define workflow state schema
✅ Cross-Workflow Coordination Tests should calculate text similarity for deduplication
✅ Cross-Workflow Coordination Tests should detect potential duplication with recent articles
✅ Cross-Workflow Coordination Tests should validate metadata directory structure
✅ Cross-Workflow Coordination Tests should define quality metrics schema
✅ Multi-Language Quality Tests should generate all 14 language versions
✅ Multi-Language Quality Tests should maintain language attribute in HTML
✅ Multi-Language Quality Tests should have consistent structure across languages
✅ Multi-Language Quality Tests should maintain analytical tone across languages
✅ Multi-Language Quality Tests should have RTL direction for Hebrew articles
✅ Validation Helper Functions should correctly count words in text
✅ Validation Helper Functions should extract party mentions correctly
✅ Validation Helper Functions should detect historical markers
✅ Validation Helper Functions should detect international comparison markers
✅ Validation Helper Functions should calculate analytical depth from markers

✅ news-realtime-monitor.test.js

✅ News Realtime Monitor - Multi-Language Synchronization getAllArticlesWithLanguageInfo should collect all articles from all languages
✅ News Realtime Monitor - Multi-Language Synchronization getAllArticlesWithLanguageInfo should detect available languages for same slug across languages
✅ News Realtime Monitor - Multi-Language Synchronization getAllArticlesWithLanguageInfo should have availableLanguages with single language for unique article
✅ News Realtime Monitor - Multi-Language Synchronization getAllArticlesWithLanguageInfo should sort articles by date descending (newest first)
✅ News Realtime Monitor - Multi-Language Synchronization generateLanguageBadge should generate language badge with flag and code
✅ News Realtime Monitor - Multi-Language Synchronization generateLanguageBadge should include dir="ltr" for RTL context
✅ News Realtime Monitor - Multi-Language Synchronization generateLanguageBadge should work for all supported languages
✅ News Realtime Monitor - Multi-Language Synchronization generateAvailableLanguages should return empty string for single language
✅ News Realtime Monitor - Multi-Language Synchronization generateAvailableLanguages should generate available languages text with badges for multiple languages
✅ News Realtime Monitor - Multi-Language Synchronization generateAvailableLanguages should use correct translation for each language
✅ News Realtime Monitor - Multi-Language Synchronization Real-world Integration Tests should verify all 14 language indexes exist
✅ News Realtime Monitor - Multi-Language Synchronization Real-world Integration Tests should verify French index contains language metadata in JavaScript
✅ News Realtime Monitor - Multi-Language Synchronization Real-world Integration Tests should verify all indexes have same article data structure
✅ News Realtime Monitor - Quality Framework assessAnalyticalDepth should score high for causal reasoning
✅ News Realtime Monitor - Quality Framework assessAnalyticalDepth should score high for comparative analysis
✅ News Realtime Monitor - Quality Framework assessAnalyticalDepth should return 0 for non-analytical content
✅ News Realtime Monitor - Quality Framework assessAnalyticalDepth should cap score at 1.0
✅ News Realtime Monitor - Quality Framework countPartyPerspectives should count Swedish party mentions
✅ News Realtime Monitor - Quality Framework countPartyPerspectives should normalize party names
✅ News Realtime Monitor - Quality Framework countPartyPerspectives should return 0 for no party mentions
✅ News Realtime Monitor - Quality Framework countPartyPerspectives should handle all 8 Swedish parties
✅ News Realtime Monitor - Quality Framework countCrossReferences should detect proposition references
✅ News Realtime Monitor - Quality Framework countCrossReferences should detect committee report references
✅ News Realtime Monitor - Quality Framework countCrossReferences should detect motion references
✅ News Realtime Monitor - Quality Framework countCrossReferences should return 0 for no document references
✅ News Realtime Monitor - Quality Framework hasWhyThisMatters should detect "Why This Matters" in English
✅ News Realtime Monitor - Quality Framework hasWhyThisMatters should detect Swedish equivalents
✅ News Realtime Monitor - Quality Framework hasWhyThisMatters should return false if section missing
✅ News Realtime Monitor - Quality Framework hasHistoricalContext should detect year references
✅ News Realtime Monitor - Quality Framework hasHistoricalContext should detect "historically" keyword
✅ News Realtime Monitor - Quality Framework hasHistoricalContext should return false if no historical context
✅ News Realtime Monitor - Quality Framework calculateQualityScore should calculate score with all metrics met
✅ News Realtime Monitor - Quality Framework calculateQualityScore should calculate lower score for poor metrics
✅ News Realtime Monitor - Quality Framework calculateQualityScore should normalize party count correctly
✅ News Realtime Monitor - Quality Framework calculateQualityScore should cap score at 1.0
✅ News Realtime Monitor - Quality Framework enhanceArticleQuality integration should pass for high-quality real article
✅ News Realtime Monitor - Quality Framework enhanceArticleQuality integration should fail for non-existent article
✅ News Realtime Monitor - Quality Framework enhanceArticleQuality integration should return detailed metrics

✅ party-dashboard.test.js

✅ Party Dashboard Dashboard Structure should have party dashboard container
✅ Party Dashboard Dashboard Structure should have dashboard title and description
✅ Party Dashboard Dashboard Structure should have footer with data source attribution
✅ Party Dashboard Chart Canvas Elements should have partyEffectivenessChart canvas
✅ Party Dashboard Chart Canvas Elements partyEffectivenessChart should have ARIA role and label
✅ Party Dashboard Chart Canvas Elements partyEffectivenessChart should have screen reader only text
✅ Party Dashboard Chart Canvas Elements should have partyComparisonChart canvas
✅ Party Dashboard Chart Canvas Elements partyComparisonChart should have ARIA role and label
✅ Party Dashboard Chart Canvas Elements partyComparisonChart should have screen reader only text
✅ Party Dashboard Chart Canvas Elements should have partyMomentumChart canvas
✅ Party Dashboard Chart Canvas Elements partyMomentumChart should have ARIA role and label
✅ Party Dashboard Chart Canvas Elements partyMomentumChart should have screen reader only text
✅ Party Dashboard Chart Canvas Elements should have coalitionAlignmentChart div container
✅ Party Dashboard Accessibility should have semantic HTML structure
✅ Party Dashboard Accessibility all charts should have proper ARIA attributes
✅ Party Dashboard Accessibility should have screen reader descriptions for all charts
✅ Party Dashboard Accessibility external links should have target="_blank"
✅ Party Dashboard Party Configuration should support all 8 Swedish parties
✅ Party Dashboard Party Configuration should define party colors for Chart.js
✅ Party Dashboard Chart Types partyEffectivenessChart should expect line chart data structure
✅ Party Dashboard Chart Types partyComparisonChart should expect bar chart data structure
✅ Party Dashboard Chart Types coalitionAlignmentChart should expect matrix/heatmap structure
✅ Party Dashboard Chart Types partyMomentumChart should expect doughnut/pie chart structure
✅ Party Dashboard Data Loading Structure dashboard should be ready for real CIA CSV data
✅ Party Dashboard Empty State Handling should have structure to display empty state messages
✅ Party Dashboard Responsive Design should use dashboard-grid for responsive layout
✅ Party Dashboard Responsive Design should have chart cards for consistent styling
✅ Party Dashboard Responsive Design should have grid layout structure
✅ Party Dashboard Multi-Language Support should have structure ready for i18n translations
✅ Party Dashboard Multi-Language Support should support Swedish party name translations

✅ party-variants.test.js

✅ party-variants PARTY_VARIANTS should have all 8 Swedish parliamentary parties
✅ party-variants PARTY_VARIANTS should have canonical code and variants for each party
✅ party-variants PARTY_VARIANTS should have correct Socialdemokraterna variants
✅ party-variants PARTY_VARIANTS should have correct Moderaterna variants
✅ party-variants PARTY_VARIANTS should have correct Sverigedemokraterna variants
✅ party-variants PARTY_VARIANTS should have correct Vänsterpartiet variants
✅ party-variants PARTY_VARIANTS should have correct Miljöpartiet variants
✅ party-variants PARTY_VARIANTS should have correct Centerpartiet variants
✅ party-variants PARTY_VARIANTS should have correct Liberalerna variants
✅ party-variants PARTY_VARIANTS should have correct Kristdemokraterna variants
✅ party-variants PARTY_VARIANTS should have unique variants within each party
✅ party-variants extractPartyMentions Single party detection should detect Socialdemokraterna by full name
✅ party-variants extractPartyMentions Single party detection should detect Socialdemokraterna by abbreviation
✅ party-variants extractPartyMentions Single party detection should detect Moderaterna by full name
✅ party-variants extractPartyMentions Single party detection should detect Sverigedemokraterna
✅ party-variants extractPartyMentions Single party detection should detect Vänsterpartiet
✅ party-variants extractPartyMentions Single party detection should detect Miljöpartiet
✅ party-variants extractPartyMentions Single party detection should detect MP abbreviation after HTML tag
✅ party-variants extractPartyMentions Single party detection should detect SD abbreviation after HTML tag
✅ party-variants extractPartyMentions Single party detection should detect KD abbreviation after HTML tag
✅ party-variants extractPartyMentions Single party detection should detect Centerpartiet
✅ party-variants extractPartyMentions Single party detection should detect Liberalerna
✅ party-variants extractPartyMentions Single party detection should detect Kristdemokraterna
✅ party-variants extractPartyMentions Multiple parties detection should detect two parties
✅ party-variants extractPartyMentions Multiple parties detection should detect three parties
✅ party-variants extractPartyMentions Multiple parties detection should detect all eight parties
✅ party-variants extractPartyMentions Multiple parties detection should detect mix of full names and abbreviations
✅ party-variants extractPartyMentions No double-counting should count party once when both full name and abbreviation appear
✅ party-variants extractPartyMentions No double-counting should count party once when full name appears multiple times
✅ party-variants extractPartyMentions No double-counting should count party once when abbreviation appears multiple times
✅ party-variants extractPartyMentions No double-counting should prevent double-counting in complex scenario
✅ party-variants extractPartyMentions Case-insensitive matching should detect lowercase party names
✅ party-variants extractPartyMentions Case-insensitive matching should detect uppercase party abbreviations
✅ party-variants extractPartyMentions Case-insensitive matching should detect mixed case party names
✅ party-variants extractPartyMentions Word boundary matching should match full word "S" not partial "SD"
✅ party-variants extractPartyMentions Word boundary matching should match full word "M" not partial "MP"
✅ party-variants extractPartyMentions Word boundary matching should not match party name as substring of another word
✅ party-variants extractPartyMentions Word boundary matching should match party name with punctuation
✅ party-variants extractPartyMentions Word boundary matching should match party name at start of sentence
✅ party-variants extractPartyMentions Word boundary matching should match party name at end of sentence
✅ party-variants extractPartyMentions Edge cases should return empty Set for empty string
✅ party-variants extractPartyMentions Edge cases should return empty Set for null input
✅ party-variants extractPartyMentions Edge cases should return empty Set for undefined input
✅ party-variants extractPartyMentions Edge cases should return empty Set for text without party mentions
✅ party-variants extractPartyMentions Edge cases should handle HTML with tags and attributes
✅ party-variants extractPartyMentions Edge cases should handle HTML entities
✅ party-variants extractPartyMentions Edge cases should handle newlines and multiple spaces
✅ party-variants extractPartyMentions Returns Set should return a Set instance
✅ party-variants extractPartyMentions Returns Set should return canonical codes not variants
✅ party-variants extractPartyMentions Returns Set should be iterable

✅ risk-dashboard.test.js

✅ Risk Dashboard Risk Level Configuration should define all four risk levels
✅ Risk Dashboard Risk Level Configuration should have non-overlapping score ranges
✅ Risk Dashboard Risk Level Configuration should have valid hex color codes
✅ Risk Dashboard Risk Level Configuration should have human-readable labels
✅ Risk Dashboard Risk Level Configuration should cover full 0-10 score range
✅ Risk Dashboard Party Colors Configuration should define colors for all 8 Swedish parties
✅ Risk Dashboard Party Colors Configuration should include all expected party abbreviations
✅ Risk Dashboard Party Colors Configuration should have valid hex color codes
✅ Risk Dashboard Party Colors Configuration should have distinct colors for each party
✅ Risk Dashboard CIA Data URLs Configuration should define 9 data source URLs
✅ Risk Dashboard CIA Data URLs Configuration should point to GitHub raw content
✅ Risk Dashboard CIA Data URLs Configuration should reference CSV files
✅ Risk Dashboard CIA Data URLs Configuration should reference sample-data directory
✅ Risk Dashboard CIA Data URLs Configuration should include risk-related datasets
✅ Risk Dashboard CIA Data URLs Configuration should include anomaly datasets
✅ Risk Dashboard CIA Data URLs Configuration should include top-10 datasets
✅ Risk Dashboard Risk Classification should classify scores 8.0-10.0 as CRITICAL
✅ Risk Dashboard Risk Classification should classify scores 6.0-7.99 as HIGH
✅ Risk Dashboard Risk Classification should classify scores 4.0-5.99 as MEDIUM
✅ Risk Dashboard Risk Classification should classify scores 0.0-3.99 as LOW
✅ Risk Dashboard Risk Classification should handle boundary values correctly
✅ Risk Dashboard Risk Color Mapping should return red for critical scores
✅ Risk Dashboard Risk Color Mapping should return orange for high scores
✅ Risk Dashboard Risk Color Mapping should return yellow for medium scores
✅ Risk Dashboard Risk Color Mapping should return green for low scores
✅ Risk Dashboard Mock Risk Data Generation should generate 15,705 data points (349 MPs × 45 rules)
✅ Risk Dashboard Mock Risk Data Generation should assign all 8 parties to MPs
✅ Risk Dashboard Mock Risk Data Generation should generate 349 unique politicians
✅ Risk Dashboard Mock Risk Data Generation should generate 45 unique rules
✅ Risk Dashboard Mock Risk Data Generation should generate scores within 0-10 range
✅ Risk Dashboard Mock Risk Data Generation should have proper data structure for each entry
✅ Risk Dashboard Mock Risk Data Generation should generate realistic risk distribution (majority low)
✅ Risk Dashboard Mock Risk Data Generation should assign consistent level labels
✅ Risk Dashboard Mock Risk Data Generation should format politician names with zero-padded index
✅ Risk Dashboard Mock Risk Data Generation should format rule IDs with zero-padded index
✅ Risk Dashboard Percentile Calculation should calculate P50 (median) correctly
✅ Risk Dashboard Percentile Calculation should calculate P90 correctly
✅ Risk Dashboard Percentile Calculation should calculate P99 correctly
✅ Risk Dashboard Percentile Calculation should handle single-element arrays
✅ Risk Dashboard Percentile Calculation should handle unsorted input
✅ Risk Dashboard Percentile Calculation should not mutate original array
✅ Risk Dashboard DOM Structure should have risk dashboard section
✅ Risk Dashboard DOM Structure should have dashboard-container class
✅ Risk Dashboard DOM Structure should have early warnings banner with ARIA attributes
✅ Risk Dashboard DOM Structure should have risk heat map container
✅ Risk Dashboard DOM Structure should have heat map legend
✅ Risk Dashboard DOM Structure should have all chart canvases
✅ Risk Dashboard DOM Structure should have top 10 lists
✅ Risk Dashboard DOM Structure should have last updated span
✅ Risk Dashboard DOM Structure should have filter controls
✅ Risk Dashboard DOM Structure should have accessible chart canvases with role=img
✅ Risk Dashboard DOM Structure should have aria-labels on chart canvases
✅ Risk Dashboard DOM Structure should have accessible top 10 lists with aria-labels
✅ Risk Dashboard Filter Controls should have high-risk filter checkbox
✅ Risk Dashboard Filter Controls should have risk rule filter dropdown
✅ Risk Dashboard Filter Controls should have "All Rules" default option
✅ Risk Dashboard Filter Controls should have reset zoom button
✅ Risk Dashboard Early Warning System should display critical alert when critical MPs exist
✅ Risk Dashboard Early Warning System should display high alert for elevated risk
✅ Risk Dashboard Early Warning System should display normal status when risks are acceptable
✅ Risk Dashboard Early Warning System should set assertive aria-live for critical alerts
✅ Risk Dashboard Early Warning System should set polite aria-live for non-critical alerts
✅ Risk Dashboard CIA Data Loading should handle successful CSV fetch
✅ Risk Dashboard CIA Data Loading should handle failed CSV fetch gracefully
✅ Risk Dashboard CIA Data Loading should handle network errors gracefully
✅ Risk Dashboard CIA Data Loading should parse risk_level CSV columns
✅ Risk Dashboard CIA Data Loading should parse politician_count as integer
✅ Risk Dashboard CIA Data Loading should transform risk data into matrix format
✅ Risk Dashboard Chart.js Visualizations should have canvas context for risk distribution chart
✅ Risk Dashboard Chart.js Visualizations should have canvas context for anomaly detection chart
✅ Risk Dashboard Chart.js Visualizations should have canvas context for crisis resilience chart
✅ Risk Dashboard Chart.js Visualizations should have canvas context for risk evolution chart
✅ Risk Dashboard Chart.js Visualizations should create risk distribution chart with bar type
✅ Risk Dashboard Chart.js Visualizations should create anomaly detection chart with scatter type
✅ Risk Dashboard Chart.js Visualizations should create crisis resilience chart with radar type
✅ Risk Dashboard Chart.js Visualizations should create risk evolution chart with line type
✅ Risk Dashboard Top 10 Lists should populate ethics concerns list with OL items
✅ Risk Dashboard Top 10 Lists should populate electoral risk list with OL items
✅ Risk Dashboard Top 10 Lists should sort ethics concerns by descending score
✅ Risk Dashboard Heat Map Legend should render 4 legend items
✅ Risk Dashboard Data Attribution should have data source link to CIA Platform
✅ Risk Dashboard Data Attribution should have external link safety attributes
✅ Risk Dashboard Data Attribution should display last updated timestamp placeholder
✅ Risk Dashboard Data Attribution should update timestamp with locale format

✅ sitemap-generation.test.js

✅ Sitemap Generation Basic Structure should generate valid XML string
✅ Sitemap Generation Basic Structure should be valid XML
✅ Sitemap Generation Basic Structure should have URL entries
✅ Sitemap Generation Basic Structure should have hreflang support
✅ Sitemap Generation Main Pages Coverage should include main index page
✅ Sitemap Generation Main Pages Coverage should include all 14 language index pages
✅ Sitemap Generation Main Pages Coverage should include politician dashboard
✅ Sitemap Generation Dashboard Pages Coverage should include English dashboard
✅ Sitemap Generation Dashboard Pages Coverage should include dashboard pages for all languages
✅ Sitemap Generation News Articles Coverage should include news index page
✅ Sitemap Generation News Articles Coverage should include news articles
✅ Sitemap Generation News Articles Coverage should include articles in multiple languages
✅ Sitemap Generation News Articles Coverage should include hreflang alternates for news articles
✅ Sitemap Generation API Documentation Coverage should include API index page
✅ Sitemap Generation API Documentation Coverage should include API documentation files
✅ Sitemap Generation API Documentation Coverage should include module documentation
✅ Sitemap Generation API Documentation Coverage should include script documentation
✅ Sitemap Generation Sitemap HTML Pages Coverage should include sitemap HTML pages
✅ Sitemap Generation Sitemap HTML Pages Coverage should include sitemap pages for multiple languages
✅ Sitemap Generation URL Quality should have proper lastmod dates
✅ Sitemap Generation URL Quality should have changefreq values
✅ Sitemap Generation URL Quality should have priority values
✅ Sitemap Generation URL Quality should use proper base URL
✅ Sitemap Generation URL Quality should not have duplicate URLs
✅ Sitemap Generation File Size and Performance should be under 50MB (sitemap limit)
✅ Sitemap Generation File Size and Performance should have less than 50,000 URLs (sitemap limit)

✅ validate-news-translations.test.js

✅ validate-news-translations.js Language code detection should detect English files
✅ validate-news-translations.js Language code detection should skip Swedish files
✅ validate-news-translations.js Language code detection should handle files without language code
✅ validate-news-translations.js Untranslated marker detection should detect untranslated markers
✅ validate-news-translations.js Untranslated marker detection should pass validation for fully translated files
✅ validate-news-translations.js Untranslated marker detection should extract sample untranslated text
✅ validate-news-translations.js Multiple file validation should validate multiple language files
✅ validate-news-translations.js Multiple file validation should report mixed results
✅ validate-news-translations.js Recursive directory scanning should scan subdirectories
✅ validate-news-translations.js Exit codes should exit with 0 for fully translated articles
✅ validate-news-translations.js Exit codes should exit with 1 for untranslated content
✅ validate-news-translations.js CJK and RTL language support should validate CJK languages
✅ validate-news-translations.js CJK and RTL language support should validate RTL languages

✅ workflow-state-coordinator.test.js

✅ Workflow State Coordinator State Management should initialize with empty state
✅ Workflow State Coordinator State Management should save and load state
✅ Workflow State Coordinator State Management should create metadata directory if missing
✅ Workflow State Coordinator State Management should set lastUpdate timestamp on save
✅ Workflow State Coordinator MCP Query Caching should cache MCP query result
✅ Workflow State Coordinator MCP Query Caching should retrieve cached MCP query
✅ Workflow State Coordinator MCP Query Caching should return null for non-existent cache key
✅ Workflow State Coordinator MCP Query Caching should expire cache after TTL
✅ Workflow State Coordinator MCP Query Caching should include result hash in cache entry
✅ Workflow State Coordinator Recent Article Tracking should add recent article
✅ Workflow State Coordinator Recent Article Tracking should set timestamp on article addition
✅ Workflow State Coordinator Recent Article Tracking should get recent articles within time window
✅ Workflow State Coordinator Recent Article Tracking should cleanup expired articles
✅ Workflow State Coordinator Duplicate Detection should detect duplicate with high title similarity
✅ Workflow State Coordinator Duplicate Detection should not flag as duplicate with low similarity
✅ Workflow State Coordinator Duplicate Detection should consider topic overlap in similarity
✅ Workflow State Coordinator Duplicate Detection should return matched article details when duplicate found
✅ Workflow State Coordinator Similarity Calculations should calculate string similarity correctly
✅ Workflow State Coordinator Similarity Calculations should calculate set overlap correctly
✅ Workflow State Coordinator Similarity Calculations should handle empty sets in overlap calculation
✅ Workflow State Coordinator Similarity Calculations should combine factors in similarity calculation
✅ Workflow State Coordinator Workflow Recording should record workflow execution
✅ Workflow State Coordinator Workflow Recording should increment run count on multiple executions
✅ Workflow State Coordinator Workflow Recording should track articles generated across runs
✅ Workflow State Coordinator Workflow Recording should get workflow statistics

✅ breaking-news.test.js

✅ Breaking News Article Generation Configuration should export REQUIRED_TOOLS constant
✅ Breaking News Article Generation Event-Driven Generation should require event data
✅ Breaking News Article Generation Event-Driven Generation should generate with event data
✅ Breaking News Article Generation Event-Driven Generation should fetch votes if voteId provided
✅ Breaking News Article Generation Event-Driven Generation should fetch speeches if topic provided
✅ Breaking News Article Generation Article Structure should generate breaking news slug
✅ Breaking News Article Generation Article Structure should generate for multiple languages
✅ Breaking News Article Generation Validation should export validateBreakingNews function
✅ Breaking News Article Generation Validation should validate breaking event content
✅ Breaking News Article Generation Validation should check for timeliness
✅ Breaking News Article Generation Multi-Language should generate language-specific titles

✅ committee-reports.test.js

✅ Committee Reports Article Generation Configuration should export REQUIRED_TOOLS constant
✅ Committee Reports Article Generation Configuration should require betankanden tool
✅ Committee Reports Article Generation Configuration should only list tools actually used by generateCommitteeReports
✅ Committee Reports Article Generation Cross-Referencing Pattern should call betankanden MCP tool
✅ Committee Reports Article Generation Cross-Referencing Pattern should fetch specified number of reports
✅ Committee Reports Article Generation Cross-Referencing Pattern should use default limit of 10 reports
✅ Committee Reports Article Generation Cross-Referencing Pattern should track MCP calls for validation
✅ Committee Reports Article Generation Data Handling should handle empty reports gracefully
✅ Committee Reports Article Generation Data Handling should skip generation when no reports found
✅ Committee Reports Article Generation Data Handling should process reports data correctly
✅ Committee Reports Article Generation Article Structure should generate articles for all requested languages
✅ Committee Reports Article Generation Article Structure should include correct slug format
✅ Committee Reports Article Generation Article Structure should generate HTML content for each language
✅ Committee Reports Article Generation Article Structure should include filename for each article
✅ Committee Reports Article Generation Committee Analysis should include report count in metadata
✅ Committee Reports Article Generation Committee Analysis should track betankanden as data source
✅ Committee Reports Article Generation Validation Functions should export validateCommitteeReports function
✅ Committee Reports Article Generation Validation Functions should validate article has committee reports
✅ Committee Reports Article Generation Validation Functions should check for minimum sources
✅ Committee Reports Article Generation Validation Functions should check for analysis tone
✅ Committee Reports Article Generation Validation Functions should check for party positions
✅ Committee Reports Article Generation Multi-Language Support should generate language-specific titles
✅ Committee Reports Article Generation Multi-Language Support should support all 14 languages
✅ Committee Reports Article Generation Error Handling should return success false on MCP error
✅ Committee Reports Article Generation Error Handling should include error message in result
✅ Committee Reports Article Generation Integration with Writer should call writeArticle function if provided
✅ Committee Reports Article Generation Integration with Writer should work without writeArticle function

✅ motions.test.js

✅ Motions Article Generation Configuration should export REQUIRED_TOOLS constant
✅ Motions Article Generation Data Collection should fetch motions from MCP
✅ Motions Article Generation Data Collection should handle empty motions
✅ Motions Article Generation Article Structure should generate articles for requested languages
✅ Motions Article Generation Article Structure should include correct slug format
✅ Motions Article Generation Validation should export validateMotions function
✅ Motions Article Generation Validation should validate motions content
✅ Motions Article Generation Multi-Language should generate language-specific titles
✅ Motions Article Generation Error Handling should handle MCP errors

✅ propositions.test.js

✅ Propositions Article Generation Configuration should export REQUIRED_TOOLS constant
✅ Propositions Article Generation Data Collection should fetch propositions from MCP
✅ Propositions Article Generation Data Collection should handle empty propositions
✅ Propositions Article Generation Article Structure should generate articles for requested languages
✅ Propositions Article Generation Article Structure should include correct slug format
✅ Propositions Article Generation Validation should export validatePropositions function
✅ Propositions Article Generation Validation should validate propositions content
✅ Propositions Article Generation Multi-Language should generate language-specific titles
✅ Propositions Article Generation Error Handling should handle MCP errors

✅ week-ahead.test.js

✅ Week-Ahead Article Generation Configuration should export REQUIRED_TOOLS constant
✅ Week-Ahead Article Generation Configuration should require calendar_events tool
✅ Week-Ahead Article Generation Configuration should only list tools actually used by generateWeekAhead
✅ Week-Ahead Article Generation Date Range Calculation should export getWeekAheadDateRange function
✅ Week-Ahead Article Generation Date Range Calculation should return date range starting tomorrow
✅ Week-Ahead Article Generation Date Range Calculation should return 7-day range
✅ Week-Ahead Article Generation Date Range Calculation should return ISO date format (YYYY-MM-DD)
✅ Week-Ahead Article Generation Data Collection should fetch calendar events for next 7 days
✅ Week-Ahead Article Generation Data Collection should pass correct date range to MCP client
✅ Week-Ahead Article Generation Data Collection should handle MCP client errors gracefully
✅ Week-Ahead Article Generation Data Collection should track MCP calls for validation
✅ Week-Ahead Article Generation Article Structure should generate articles for all requested languages
✅ Week-Ahead Article Generation Article Structure should generate EN version by default
✅ Week-Ahead Article Generation Article Structure should generate SV version by default
✅ Week-Ahead Article Generation Article Structure should include correct slug format
✅ Week-Ahead Article Generation Article Structure should generate HTML content for each language
✅ Week-Ahead Article Generation Article Structure should include filename for each article
✅ Week-Ahead Article Generation Cross-Referencing should include cross-reference data in result
✅ Week-Ahead Article Generation Cross-Referencing should track calendar events count
✅ Week-Ahead Article Generation Cross-Referencing should list data sources used
✅ Week-Ahead Article Generation Validation Functions should export validateWeekAhead function
✅ Week-Ahead Article Generation Validation Functions should validate article has calendar events
✅ Week-Ahead Article Generation Validation Functions should check for minimum sources
✅ Week-Ahead Article Generation Validation Functions should check for prospective tone
✅ Week-Ahead Article Generation Validation Functions should check daily coverage
✅ Week-Ahead Article Generation Multi-Language Support should support all 14 languages
✅ Week-Ahead Article Generation Multi-Language Support should generate language-specific titles
✅ Week-Ahead Article Generation Multi-Language Support should handle RTL languages (ar, he)
✅ Week-Ahead Article Generation Error Handling should return success false on MCP error
✅ Week-Ahead Article Generation Error Handling should include error message in result
✅ Week-Ahead Article Generation Error Handling should still return mcpCalls on error
✅ Week-Ahead Article Generation Integration with Writer should call writeArticle function if provided
✅ Week-Ahead Article Generation Integration with Writer should pass html and filename to writer
✅ Week-Ahead Article Generation Integration with Writer should work without writeArticle function

← Back to Documentation Hub