Skip to content
Snippets Groups Projects
Commit aae200e6 authored by Adam G-H's avatar Adam G-H
Browse files

Issue #3311001 by phenaproxima: Document the fixtures used by StagedProjectsValidatorTest

parent d2477c64
No related branches found
No related tags found
1 merge request!489Issue #3311001: Document the fixtures used by StagedProjectsValidatorTest
Showing
with 30 additions and 27 deletions
# `StagedProjectsValidatorTest` Fixtures
### new_project_added
Simulates a scenario where, while updating Drupal core in a site with no non-core dependencies, a new contrib module and
a new custom module are unexpectedly installed (as runtime and dev dependencies, respectively). Additionally, two new
non-Drupal packages are installed (again, one as a runtime dependency, the other dev).
**Expectation**: The validator should complain about the new modules; the new non-Drupal packages are ignored.
### no_errors
Simulates a scenario where, while updating Drupal core in a site with two unpinned contrib dependencies (one runtime and
one dev), no Drupal packages are updated, but two non-Drupal libraries are removed (again, one a runtime dependency, the
other dev), two are updated (same arrangement), and two are added (ditto).
**Expectation**: The validator to raise no errors; changes to non-Drupal packages are ignored.
### project_removed
Simulates a scenario where, while updating Drupal core in a site with no non-core dependencies, an installed contrib
theme and an installed custom theme are unexpectedly removed (from runtime and dev dependencies, respectively).
Additionally, two installed non-Drupal packages are removed (again, one from a runtime dependency, the other dev). The
existing contrib dependencies' installed versions are unchanged.
**Expectation**: The validator should complain about the removed themes; the removed non-Drupal packages are ignored.
### version_changed
Simulates a scenario where, while updating Drupal core in a site with two unpinned contrib dependencies (one runtime and
one dev), the contrib modules are unexpectedly updated, as are two installed non-Drupal packages (again, one a runtime
dependency, the other dev).
**Expectation**: The validator should complain about the updated modules; the updated non-Drupal packages are ignored.
{
"require": {
"drupal/core-composer-scaffold": "*",
"drupal/core-vendor-hardening": "*",
"drupal/core-project-message": "*",
"drupal/core-dev": "*",
"drupal/core-dev-pinned": "*"
},
"extra": {
"_comment": [
"This is an example composer.json that does not require Drupal core.",
"@see \\Drupal\\Tests\\automatic_updates\\Kernel\\ReadinessValidation\\CoreComposerValidatorTest"
]
}
}
{
"packages": [
{
"name": "drupal/core-recommended",
"version": "9.8.0"
},
{
"name": "drupal/core",
"version": "9.8.0"
}
]
}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment