You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/08/18 20:16:20 UTC
[jira] [Commented] (CB-6724) manual tests should have docs
indicating the expected result
[ https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14100986#comment-14100986 ]
ASF GitHub Bot commented on CB-6724:
------------------------------------
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-battery-status/pull/16
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-battery-status CB-6724
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-battery-status/pull/16.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 #16
----
commit 6be10452d14c9b944b8f7cc30c6787565e366b4c
Author: Edna Morales <ed...@ednas-mbp-2.raleigh.ibm.com>
Date: 2014-07-29T19:01:48Z
added documentation for manual tests
commit c95343e22a60882d01caa41abf4e77f65243e923
Author: Edna Morales <ed...@ednas-mbp-2.raleigh.ibm.com>
Date: 2014-08-13T16:25:49Z
merged with new tests folder
commit 08ad91f4ab289e7d7695300da56e741a84f41a17
Author: Edna Morales <ed...@ednas-mbp-2.raleigh.ibm.com>
Date: 2014-08-18T18:10:43Z
cb6724re-add accidental removed of var keyword
----
> 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)