[
https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100990#comment-14100990
]
ASF GitHub Bot commented on CB-6724:
------------------------------------
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-contacts/pull/42
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-contacts CB-6724
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-contacts/pull/42.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 #42
----
commit 52b82130b4e40eae58482f1ede86b1067bc88e27
Author: Staci Cooper <[email protected]>
Date: 2014-07-18T18:48:52Z
merged changes for test framework plugin
commit a67a8a9dd095267dea0226727389a33dc20fc060
Author: Edna Morales <[email protected]>
Date: 2014-07-29T16:58:46Z
added documentation for manual tests
commit e73c224ceca90479cf644526cbdf564f745530ac
Author: Edna Morales <[email protected]>
Date: 2014-08-13T16:42:10Z
Merge renamed tests directory
commit adf7f1a6dc6a3208eb9283b52a054acd28341a4b
Author: Edna Morales <[email protected]>
Date: 2014-08-13T16:45:52Z
rm old test folder and merged with renamed tests folder
commit 46f4fe32b8cf433f18407a827a2ef86dd2351b3b
Author: Edna Morales <[email protected]>
Date: 2014-08-18T15:36:20Z
rebasing from master
----
> 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)
