cordova-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101030#comment-14101030
] 

ASF GitHub Bot commented on CB-6724:
------------------------------------

GitHub user eymorale opened a pull request:

    https://github.com/apache/cordova-plugin-vibration/pull/20

    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-vibration CB-6724

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

    https://github.com/apache/cordova-plugin-vibration/pull/20.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 #20
    
----
commit 27bf922b18e8ca65a9c2decc4531492722ff5c70
Author: Edna Morales <ednamorales@ednas-mbp-2.raleigh.ibm.com>
Date:   2014-08-18T17:51:25Z

    cb-6724documented Windows support for vibrate with pattern and cancel vibrate in manual
test doc and moved tests to tests dir

----


> 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)

Mime
View raw message