Test auto-discovery in List Command

Author: Bellangelo

tests/Command/WorkspaceListCommandTest.php

@@ -62,11 +62,11 @@ public function testExecute()
         $configContent = file_get_contents('adr.yml');
         $configContent = str_replace('docs/arch', $vfs->url(), $configContent);
         $configContent = str_replace('vendor/bellangelo/phpadr/', '', $configContent);
-        $configFile = vfsStream::newFile('adr.yml')->at($vfs)->setContent($configContent)->url();
+        $configFile = vfsStream::newFile('adr-test.yml')->at($vfs)->setContent($configContent);
 
         $input = [
             'command'  => $this->command->getName(),
-            '--config' => $configFile,
+            '--config' => $configFile->url(),
         ];
 
         (new Application())->add($this->command);
@@ -84,4 +84,27 @@ public function testExecute()
         $this->assertStringContainsString('0001-foo.md', $tester->getDisplay());
         $this->assertStringContainsString('0002-bar.md', $tester->getDisplay());
     }
+
+    public function testExecuteWithAutoDiscovery()
+    {
+        $originalValue = $GLOBALS['_composer_autoload_path'] ?? '';
+        $GLOBALS['_composer_autoload_path'] = __DIR__ . '/../data/vendor/autoload.php';
+
+        try {
+            $input = [
+                'command' => $this->command->getName(),
+            ];
+
+            (new Application())->add($this->command);
+
+            $tester = new CommandTester($this->command);
+            $tester->execute($input);
+
+            $this->assertStringContainsString('0001-test1.md', $tester->getDisplay());
+            $this->assertStringContainsString('0002-test2.md', $tester->getDisplay());
+
+        } finally {
+            $GLOBALS['_composer_autoload_path'] = $originalValue;
+        }
+    }
 }

tests/data/adr.yml

@@ -0,0 +1,3 @@
+directory: tests/data/docs/arch
+template:
+  decision-record: ./skeleton.md

tests/data/docs/arch/0001-test1.md

@@ -0,0 +1,19 @@
+# 1. Documenting architecture decisions
+
+Date: 2018-02-11
+
+## Status
+
+Accepted
+
+## Context
+
+Record certain design decisions for the benefit of future team members as well as for external oversight.
+
+## Decision
+
+Use Architecture Decision Records (ADR), that is a technique for capturing important architectural decisions, along with their context and consequences as described by [Michael Nygard](https://twitter.com/mtnygard) in his article: [Documenting Architecture Decisions](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions).
+
+## Consequences
+
+See Michael Nygard's article, linked above.

tests/data/docs/arch/0002-test2.md

@@ -0,0 +1,23 @@
+# 2. Develop tool to manage ADRs
+
+Date: 2018-02-12
+
+## Status
+
+Accepted
+
+## Context
+
+Encourage and facilitate the use of documentation in agile projects in world of evolutionary architecture using the technique Architecture Decision Records (ADR).
+
+## Decision
+
+Develop a command-line tool to manage the Architecture Decision Records (ADR) that will be stored in version control along with the project source code.
+
+## Consequences
+
+It is very easy for the development team to use.
+
+Project managers, client stakeholders, and others who don't work in version control like the development team, they will can to have difficulty using the tool or not using.
+
+But these people can help to manage Architecture Decision Records (ADR), because the records can be created or edited by a web-based version control repository hosting service, for example: Github, Bitbucket or others.

tests/data/skeleton.md

@@ -0,0 +1,13 @@
+# <sequence>. <title>
+
+Date: <date>
+
+## Status
+
+<status>
+
+## Context
+
+## Decision
+
+## Consequences