When setting 'exclude' as an array of pattern values only the last value processed is considered

[DaJoTo]

This appears to be a bug with Beta version 1.0.8 of Nightwatch.js

Consider the following test suite directory:

• group1
  • subGroupA
    • test1.js
    • test2.js
  • subGroupB
    • test1.js
    • test2.js
  • subGroupC
    • test1.js
    • test2.js
• group2
  • subGroupA
    • test1.js
    • test2.js
  • subGroupB
    • test1.js
    • test2.js
  • subGroupC
    • test1.js
    • test2.js

Now consider the default environment using the matches

const jar = require('selenium-server-standalone-jar');

module.exports = {
    src_folders: 'tests',
    output_folder: 'output',
    globals_path: 'globals.js',
    selenium: {
        start_process: true,
        server_path: jar.path,
        log_path: '',
        cli_args: {
            'webdriver.chrome.driver': 'node_modules/.bin/chromedriver',
            'webdriver.gecko.driver': 'node_modules/.bin/geckodriver',
        },
    },
    test_settings: {
        default: {
            launch_url: 'http://localhost:8069',
            desiredCapabilities: {
                browserName: 'firefox',
            },
            exclude: [
                'group1/subGroupA/test2.js',
                'group1/subGroupB/test1.js',
            ],
        },
        chrome: {
            desiredCapabilities: {
                browserName: 'chrome',
            },
        },
    },
};

When running the tests you will find that test group1/subGroupA/test2.js will still be run because matches is evaluated per iteration of the exclude patterns. Meaning while it was true for the first iteration, the second (last) was false.

[beatfactor]

Can you also include your nightwatch config? Thanks.

[DaJoTo]

@beatfactor I've updated with a config file