ldgit / argus Goto Github PK

Because of course not...

... and run it on each build.

The official docs are here.

Currently, argus needs to restarted in order to watch new tests. This could be changed so that test file creation is detected automatically and new tests and source files added to watchlist.

This is an issue on chokidar when watching specific files instead of directories.
Proposed solution is to turn the filepath into a glob that would only watch that file.

Some basic user commands to implement:

• press l to list all available commands
• press a to run all tests - this would simply run testRunnerCommand from each environment without any file arguments
• press r to rerun last run batch of tests

Default configuration was unnecessarily specific to PHP.

This is related to chokidar bug that causes ready event to never fire when watching globs with nonexisting directories or files.

Breaks on Windows 10 (powershell).

For example, if npm t runs all our unit tests, current test runner command format would be:

module.exports = {
    {
      // ...
      arguments: ['t', '--'],      
      testRunnerCommand: 'npm',
      // ...
    },
  ],
};

New format:

module.exports = {
    {
      // ...
      testRunnerCommand: { command: 'npm', arguments: ['t', '--'] },
      // ...
    },
  ],
};

This would make it consistent with the format of runAllTestsCommand.

Current behavior if no test file found is to run all the tests for project.

More info can be found here:

• paulmillr/chokidar#624
• https://stackoverflow.com/questions/16748737/grunt-watch-error-waiting-fatal-error-watch-enospc
• https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached

Users should be able to tell argus what files to watch and how to run tests on them if they change.
To support this, user should define special config file.

Current proposal is a javascript module describing different environments, for example:

module.exports = {
  environments: [
    {
      extension: 'php',
      testNameSuffix: 'Test',
      testDir: 'tests/unit',
      sourceDir: 'src',
      arguments: ['--colors'],
      testRunnerCommand: 'vendor/bin/phpunit',
    },
    {
      extension: 'js',
      testNameSuffix: '.test',
      testDir: 'tests/unit',
      sourceDir: 'src',
      arguments: [],
      testRunnerCommand: 'node_modules/.bin/mocha',
    },
  ],
};

This would have following benefits:

• could watch and run tests for different languages, e. g. javascript and PHP
• would support watching tests in same language with different configurations, e. g. unit and integration test configuration, all at the same time
• would solve #3
• is flexible enough to easily support further expansion in the future, e. g. user could provide a custom locator function for finding source files for a given test file

To mantain BC, if no configuration file is found a special default configuration will be used.

For example, print info message if test not found for file.

Add verbose CLI option (-v) that could show more info in terminal:

• print a list of files watched
• print the console command that was run