[Feature] CLI Test Coverage

I’m submitting a feature request

• Library Version: 0.19.0

Please tell us about your environment:

• Operating System: All

• Node Version: 6.6.0

• NPM Version: 3.10.3

• Browser: all

• Language: all

Current behavior: No test coverage of Aurelia CLI behaviors and functions

Expected/desired behavior:

• What is the expected behavior? Test coverage should exist for the CLI to protect from regression issues and ensure good code quality
• What is the motivation / use case for changing the behavior? Adding new features to the CLI can cause regression issues, among other things. To protect against regression issues, and to ensure that the CLI is behaving as expected, tests should exist.

[s-hoff]

I just managed to get a test running on the file-system.js using mock-fs and jasmine-node. I tried all the functions on file-system and fs that are being called on the code according to a search all ‘fs’ with vscode.

The only limitation I hit was that the (deprecated) exists() function did not work at all. It is used a total of 6 times in the code, all in the cli’s own files.

If we replace exists() with fs.stat() and fs.access(), it should work with mock-fs.

[MeirionHughes]

I assume this can be closed now