GitHub user benkeen opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/172

    Refactor Nightwatch

    This ticket makes a few changes to the way Nightwatch is set up:
    1. the main Nightwatch settings (username, password, login URL, key
    nightwatch setup file locations) are moved to the settings.json
    file to allow them to be defined a single global place and overridden
    if need be.
    2. it now dynamically determines the list of tests to run based on
    content of settings.json.
    3. hardcoded username, password & URL moved from helpers.js and
    loginToGUI.js and now loaded from settings.json file
    
    Closes COUCHDB-2481

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benkeen/couchdb-fauxton 
2481-nightwatch-refactor

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/172.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #172
    
----
commit 8757d6c6e6772d81a04563a1d50683179c4a055a
Author: Benjamin Keen <[email protected]>
Date:   2014-11-26T20:54:03Z

    Refactor Nightwatch
    
    This ticket makes a few changes to the way Nightwatch is set up:
    1. the main Nightwatch settings (username, password, login URL, key
    nightwatch setup file locations) are moved to the settings.json
    file to allow them to be defined a single global place and overridden
    if need be.
    2. it now dynamically determines the list of tests to run based on
    content of settings.json.
    3. hardcoded username, password & URL moved from helpers.js and
    loginToGUI.js and now loaded from settings.json file
    
    Closes COUCHDB-2481

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to