GitHub user jpchase opened a pull request:

    https://github.com/apache/cordova-plugin-test-framework/pull/6

    CB-7459 Add header to show number of enabled plugin tests

    It is not obvious if all/how many plugin tests are being run, given that:
    - Individual plugin tests can be enabled/disabled by the user
    - The enabled settings are remembered across app runs (even if the user 
forgets)
    - The UI widgets to enable/disable individual plugins is hidden in a 
collapsed
     section by default, so are not visible
    
    To aid the user, a header has been added to explicitly show the total 
number of
    tests, and how many are enabled (e.g. "All" vs. "N/M").

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

    $ git pull https://github.com/jpchase/cordova-plugin-test-framework 
CB-7459-part2

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

    https://github.com/apache/cordova-plugin-test-framework/pull/6.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 #6
    
----
commit 1456ebc984e93ddd7b708aa8f00ebeae32d4eea7
Author: Jason Chase <jasonpch...@gmail.com>
Date:   2014-09-15T13:55:50Z

    CB-7459 Add header to show number of enabled plugin tests
    
    It is not obvious if all/how many plugin tests are being run, given that:
    - Individual plugin tests can be enabled/disabled by the user
    - The enabled settings are remembered across app runs (even if the user 
forgets)
    - The UI widgets to enable/disable individual plugins is hidden in a 
collapsed
     section by default, so are not visible
    
    To aid the user, a header has been added to explicitly show the total 
number of
    tests, and how many are enabled (e.g. "All" vs. "N/M").

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to