[
https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102266#comment-14102266
]
ASF subversion and git services commented on CB-6724:
-----------------------------------------------------
Commit aed63c8ffe06dcf620bbf73e1e3bd6ba1f4b38f5 in
cordova-plugin-network-information's branch refs/heads/master from [~eymorale]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-network-information.git;h=aed63c8
]
CB-6724 added documentation for manual tests
github: close #17
> 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)
