Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Date: Wed, 23 Jul 2014 20:12:38 +0000 (UTC)
From: "Edna Morales (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12715472.1400592288867.31765.1406146358971@arcas>
In-Reply-To: <JIRA.12715472.1400592288867@arcas>
References: <JIRA.12715472.1400592288867@arcas>
Subject: [jira] [Assigned] (CB-6724) manual tests should have docs
 indicating the expected result
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edna Morales reassigned CB-6724:
--------------------------------

    Assignee: Edna Morales

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