Skip to content
This repository has been archived by the owner on Sep 16, 2024. It is now read-only.

Enhance Documentation - Include Test Suites #94

Open
chris-stage opened this issue Feb 14, 2019 · 0 comments
Open

Enhance Documentation - Include Test Suites #94

chris-stage opened this issue Feb 14, 2019 · 0 comments

Comments

@chris-stage
Copy link

Hey!

I am trying to use grunt-webdriver to run test suites in sequence instead of running all spec files at once. Here is my conf.js file:

`exports.config = {
//
// ====================
// Runner Configuration
// ====================
//
// WebdriverIO allows it to run your tests in arbitrary locations (e.g. locally or
// on a remote machine).
runner: 'local',

//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which `wdio` was called. Notice that, if you are calling `wdio` from an
// NPM script (see https://docs.npmjs.com/cli/run-script) then the current working
// directory is where your package.json resides, so `wdio` will be called from there.
//
specs: [
    './test/specs/login/**/*.js'
],
suites: {
    login_ui: [
        './test/specs/login/reporter_login_ui.spec.js',
        './test/specs/login/reporter_login_errors.spec.js'
    ],
    login: [
        './test/specs/login/reporter_login.spec.js',
        './test/specs/login/reporter_logout.spec.js'
    ],
    login_timeout: [
        './test/specs/login/reporter_login_timeout.spec.js',
        './test/specs/login/reporter_login_retry.spec.js'
    ],
    login_reject: [
        './test/specs/login/reporter_login_reject.spec.js'
    ]
},`

I am trying to solve the problem of having using the command line to execute suites in order:
./node_modules/.bin/wdio wdio.login.conf.js --suite login_ui
./node_modules/.bin/wdio wdio.login.conf.js --suite login
./node_modules/.bin/wdio wdio.login.conf.js --suite login_timeout

Any help would be much appreciated.

Thanks,
Chris

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant