Browse Source

Correct github issue test to include a lock file, still fails because of real bug now

Nils Adermann 5 years ago
parent
commit
48ae45e5fe
1 changed files with 16 additions and 1 deletions
  1. 16 1
      tests/Composer/Test/Fixtures/installer/github-issues-4795.test

+ 16 - 1
tests/Composer/Test/Fixtures/installer/github-issues-4795.test

@@ -30,13 +30,28 @@ dependency of one the requirements that is whitelisted for update.
     { "name": "b/b", "version": "1.0.0", "require": { "a/a": "~1.0" } }
 ]
 
+--LOCK--
+{
+    "packages": [
+        { "name": "a/a", "version": "1.0.0" },
+        { "name": "b/b", "version": "1.0.0", "require": { "a/a": "~1.0" } }
+    ],
+    "packages-dev": [],
+    "aliases": [],
+    "minimum-stability": "dev",
+    "stability-flags": [],
+    "prefer-stable": false,
+    "prefer-lowest": false,
+    "platform": [],
+    "platform-dev": []
+}
 --RUN--
 update b/b --with-dependencies
 
 --EXPECT-OUTPUT--
 <warning>Dependency "a/a" is also a root requirement, but is not explicitly whitelisted. Ignoring.</warning>
 Loading composer repositories with package information
-Updating dependencies (including require-dev)
+Updating dependencies
 Nothing to install or update
 Writing lock file
 Generating autoload files