Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Manual Test Plan #441

Merged
merged 2 commits into from Feb 25, 2015
Merged

Manual Test Plan #441

merged 2 commits into from Feb 25, 2015

Commits on Feb 25, 2015

  1. avocado-run-testplan: introduce a minimalist tool to help with manual… 

    … test plans

Some test routines can not yet be easily automated in Avocado, and for those, we
rather test things manually then not at all.

The idea behind this tool is to use a predefined test plan (a simple JSON file)
that has test names and descriptions with how to perform the test and what to
expect. The tool will ask for the results for each test (either PASS, FAIL or
SKIP) and possibly additional notes. These results will then be saved to a JSON
file or to a human readable report.

The human readable report can, for instance, be part of a release commit message,
or if preferred, the JSON result file can be committed to keep track of what is
working and what is known to be broken at a given time.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
    @clebergnu
    clebergnu committed Feb 25, 2015
    Configuration menu
    Copy the full SHA
    326453e View commit details
    Browse the repository at this point in the history

  2. [WIP] Introduce example test plan for use with avocado-run-testplan 

    This is an example test plan of what could/should be run before the
release of a new avocado version.

Signed-off-by: Cleber Rosa <crosa@redhat.com>
    @clebergnu
    clebergnu committed Feb 25, 2015
    Configuration menu
    Copy the full SHA
    5c70ab5 View commit details
    Browse the repository at this point in the history