Quality Control & Assurance Flashcards

In a Drupal CI/CD pipeline, what is the primary purpose of running `composer validate`?

Answer: Verifying that composer.json and composer.lock are consistent and well-formed

`composer validate` checks that composer.json is syntactically correct and that composer.lock matches the declared dependencies, catching drift before deployment.

What Drupal status report warning indicates a potential security risk that QA teams should address immediately?

Answer: Modules with available security updates

Modules flagged with available security updates in the Status Report represent known vulnerabilities that must be patched to protect the site.

Which approach best prevents regressions when refactoring a Drupal custom module's service class?

Answer: Writing unit tests for the service before refactoring, then verifying they still pass after

Pre-existing unit tests act as a safety net by immediately revealing if refactoring broke any expected behavior without requiring manual verification.

What does the Drupal `DeprecationHelper` (or `@trigger_error` with `E_USER_DEPRECATED`) enable in quality assurance workflows?

Answer: Flagging code paths that will break in future Drupal major versions so they can be fixed proactively

Triggering E_USER_DEPRECATED errors allows CI tools like PHPUnit's deprecation tracker to surface deprecated API usage before a major version upgrade breaks the site.

In Drupal's automated testing, what is the role of `setUp()` in a test class?

Answer: Initializes the test environment and shared state before each test method runs

`setUp()` is called before every individual test method, providing a fresh and consistent starting state to prevent test interdependence.

A QA engineer notices that a Drupal view displays incorrect results after a content type field is renamed. Which QA process would have caught this earliest?

Answer: Functional tests that assert view output after configuration changes

Functional tests that load the view and assert expected output against known content would immediately fail when the field rename breaks the view's data source.

Which Drupal module is designed to compare configuration between environments to detect unintended config drift?

Answer: Config Split combined with Config Inspector

Config Inspector (and Config Split for environment-specific splits) allows teams to compare active configuration against stored config exports to detect unintended divergence between environments.