cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-6724) manual tests should have docs indicating the expected result
Date Mon, 18 Aug 2014 18:26:19 GMT


ASF GitHub Bot commented on CB-6724:

GitHub user eymorale opened a pull request:


    documentation for manual tests

You can merge this pull request into a Git repository by running:

    $ git pull CB-6724

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #68
commit f4eb0a09612610492e10c0b7a459f0d65714cfed
Author: Edna Morales <>
Date:   2014-07-23T20:39:23Z

    Merging to work on top of test framework changes

commit 8ff7d173948beefb7864aed60170d6fe2c0d0ee0
Author: Edna Morales <>
Date:   2014-07-23T20:39:59Z

    Merging to work on top of relative paths change

commit 19f17a71e14105aa1b19edba491613afde305f13
Author: Edna Morales <>
Date:   2014-07-24T20:42:13Z

    added documentation for manual tests

commit 76f33578b5132a39db0ee73ea765e5e248a17e97
Author: Edna Morales <>
Date:   2014-08-18T15:55:52Z

    rebase from master

commit 3086907f8a99c38b3336ce6805bc9fe2ef61969b
Author: Edna Morales <>
Date:   2014-08-18T17:38:29Z

    cb-6724changed style detail on documentation


> manual tests should have docs indicating the expected result
> ------------------------------------------------------------
>                 Key: CB-6724
>                 URL:
>             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

View raw message