Quality Control & Assurance Flashcards

What is the role of a 'test fixture' in Drupal automated testing?

Answer: Pre-created content, configuration, or data used to set up a known state for tests

Test fixtures establish a deterministic starting state (nodes, users, config) so that each test runs against consistent data and produces reproducible results.

Which Drupal security hardening check should QA verify is enabled on a production site to prevent text injection via user input fields?

Answer: Filtering user input through an allowed HTML text format with XSS filtering enabled

Drupal's text format system with XSS filtering strips disallowed HTML tags from user input, preventing cross-site scripting attacks through content fields.

In a Drupal project using GitLab CI, what artifact should the PHPUnit test stage produce to allow QA review of test results?

Answer: A JUnit XML report file consumed by GitLab's test reports UI

PHPUnit can output JUnit XML via `--log-junit`, which GitLab CI's `reports: junit:` artifact key parses to display test pass/fail directly in merge request pipelines.

A QA team finds that a Drupal cron job silently fails without logging errors. What is the best practice fix?

Answer: Wrapping cron logic in try/catch blocks that log errors to Drupal's watchdog

Catching exceptions in cron implementations and logging them via \Drupal::logger() ensures failures are surfaced and actionable rather than silently swallowed.

What does `PHPStan` with the `phpstan/phpstan-drupal` extension add to a Drupal project's quality pipeline?

Answer: Static type analysis that catches type errors and undefined method calls without running the code

phpstan-drupal extends PHPStan with Drupal-specific stubs and rules so that static analysis understands Drupal's service container, entity APIs, and hook system during type checking.

Which strategy should a QA team adopt to validate that a Drupal site's Views-generated pages remain correct after a database schema change?

Answer: Automated functional tests that assert specific field values appear in the rendered view output

Functional tests that render views and assert expected field values in the HTML output will immediately fail if a schema change causes a view query to break or return unexpected data.

What is the purpose of the Drupal `upgrade_status` module in a QA workflow?

Answer: Scanning installed modules and themes for compatibility with the next major Drupal version

The upgrade_status module analyzes installed projects for deprecated API usage and flags those that need updates before a major Drupal version migration, giving QA teams a readiness checklist.