[
https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101010#comment-14101010
]
ASF GitHub Bot commented on CB-6724:
------------------------------------
GitHub user eymorale opened a pull request:
https://github.com/apache/cordova-plugin-file-transfer/pull/40
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-file-transfer CB-6724
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-file-transfer/pull/40.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 #40
----
commit 91a67f864e6e7212ac25e619583070b82610dc68
Author: Edna Morales <[email protected]>
Date: 2014-07-23T20:41:56Z
Merge to work on top of test framework changes
commit 683a0facefa7586f1c10a77124f67b8dd27ac261
Author: Edna Morales <[email protected]>
Date: 2014-07-24T18:48:35Z
added documentation to manual tests
commit 86446811b2d72dc22ecda54bf0693f6b11648e8d
Author: Edna Morales <[email protected]>
Date: 2014-08-13T17:07:30Z
Merge renamed tests dir
commit e1afbb6d24c19e5522fd646d7263d59895560232
Author: Edna Morales <[email protected]>
Date: 2014-08-18T15:59:20Z
rebase from master
commit 6f9b59fd8832b90f79c88d8a1af7369e9fadfabf
Author: Edna Morales <[email protected]>
Date: 2014-08-18T17:39:29Z
added documentation for new test
----
> 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)
