This repo contains all core gulp aut tasks which can be configured and used in any FEAR projects alltogether or individually.

The tasks in this repo are provided in a factory function format for developer convenience, so you can use the functionality but can give any name to the task you create and configure it as much as the Core Task API makes it possible (see examples below).

Installation

To use any of the provided Core gulp tasks, please install the module first:

$ npm install --save-dev mns-core-test

then to use:

require('mns-core-test');

or use the fear-core installer module here

Further reading


Changelog

5.0.1

  • fix missing name changes

5.0.0

  • module renamed to mns-core-test

4.0.1

  • updated mns-docker version, fixed chrome debug docker compose file, add firefox debug compose file

4.0.0

  • added docker compose for a test enviroment. Can be used to launch a selenium grid with chrome and firefox instances.

3.0.0

  • added default configs for webdriverio and webdrivercss

2.0.1

  • e2e taskFactory accepts options object instead of individual params

1.2.4

  • remove gulp-util in favour of process.stdout.write/chalk

1.2.3

  • add baseline clone for visual testing

1.2.2

  • add ally accessibility test tool

1.1.9

  • Added ability for visual testing to use the WebdriverCss Admin Panel

1.1.8

  • fix graphicsmagick install for windows

1.1.7

  • bug fix so browser resizing is complete before tests run

1.1.6

  • removal of global variables

1.1.5

  • upgrade phantomJS version to 2.1.3

1.1.4

  • added sass lint install to module postinstall script

1.1.3

  • added documentation

1.1.2

  • first working npm publish

Contributing

Here's the most direct way to get your work merged into the project:

If your work is a new feature or a patch then follow the following workflow

  • Fork the project.
  • Clone down your fork ( git clone git@github.com:[username]/mns-core-test.git ).
  • Create a topic branch to contain your change ( git checkout -b my_awesome_feature ).
  • Code away and add tests if applicable. Not necessarily in that order.
  • Make sure everything still passes by running npm run test.
  • Update the change log with details of the change and then mark in brackets what type of change it is (new feature/patch). The version of the next published version will then be decided by this.
  • If necessary, rebase your commits into logical chunks, without errors.
  • Push the branch up ( git push origin my_awesome_feature ).
  • Create a pull request against mns-core-test/master and describe what your change does and the why you think it should be merged.

If your work is a breaking change please come to talk to the core team before commencing development.