[
https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101016#comment-14101016
]
ASF GitHub Bot commented on CB-6724:
------------------------------------
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-network-information/pull/17
CB-6724
documentation for manual tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eymorale/cordova-plugin-network-information
CB-6724
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-network-information/pull/17.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 #17
----
commit e95173d567479ea25ee831ae958beaf33ae22cec
Author: Staci Cooper <[email protected]>
Date: 2014-07-16T17:51:46Z
CB-6964 ported manual tests
Fixed up style
commit 807f839bfe751b70f9e66d34ff80e06781f3cf81
Author: Edna Morales <[email protected]>
Date: 2014-07-28T20:43:09Z
merged changes from addEventListener typo
commit c0d76930e9c893a2ff21d21dc47fc193644b0580
Author: Edna Morales <[email protected]>
Date: 2014-07-28T20:58:13Z
added documentation for manual tests
commit cda67c838c7220051ccdd1a6ee2ff08129c9da15
Author: Edna Morales <[email protected]>
Date: 2014-08-13T17:22:05Z
Merge renamed tests dir
----
> manual tests should have docs indicating the expected result
> ------------------------------------------------------------
>
> Key: CB-6724
> URL: https://issues.apache.org/jira/browse/CB-6724
> Project: Apache Cordova
> Issue Type: Improvement
> Components: mobile-spec
> Reporter: Marcel Kinard
> Assignee: Edna Morales
> Priority: Minor
>
> The manual tests in mobile-spec have buttons that do things and test the
> functions, but there is no indication and no documentation associated with
> those tests that indicate what the expected result should be. So it becomes
> difficult to compare the expected result with the actual result, unless you
> are very familiar with the function and know in your head what the expected
> result should be. It would be good if the expected result is documented, so
> non-experts can run the manual tests and validate the results.
> The manual tests for InAppBrowser do include some documentation of the
> expected inline with the buttons, so that may be considered a prototype of
> what is needed here.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
