Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=PLATFORM_STANDARDS_MANUAL_TESTS_R1, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

In this revision the implementation of PLATFORM_STANDARDS_MANUAL_TESTS_R0 should be exported in a separate wiki pages and expanded.

Task requirements

• Research what bug types are needed for the custom fields in trac.
• Create a wiki page PLATFORM_STANDARDS_MANUAL_TESTS/TestCaseTracking? and move the corresponding section of Implementation section of PLATFORM_STANDARDS_MANUAL_TESTS_R0 in it.
• Create a wiki page PLATFORM_STANDARDS_MANUAL_TESTS/BugReporting? and move the corresponding section of Implementation section of PLATFORM_STANDARDS_MANUAL_TESTS_R0 in it.
• Create a basic test plan for testing basic features and point it in the document (in testlink).
• Define rules for bug reporting (in trac ticket system)
• Clarify aspects marked as system dependent in R0 (trac, testlink instead of tcw)
• Link the created pages in PROCESS page.
• Link the created pages in PLATFORM_STANDARDS_GENERAL

The explanation should be detailed enough to explain how these actions are accomplished in trac or testlink.

Task result

The result is wiki pages.

Implementation idea

Create a test case and a ticket for demonstration purposes, point them as examples in the documents.

Related

​http://10.10.117.11/testlink
PLATFORM_STANDARDS_MANUAL_TESTS_R0

How to demo

PLATFORM_STANDARDS_MANUAL_TESTS/TestCaseTracking?
PLATFORM_STANDARDS_MANUAL_TESTS/BugReporting?

Design

For writing manual test cases, we will use Testlink. We will use our Trac for bug reporting.

PLATFORM_STANDARDS_MANUAL_TESTS page will be created. The information in it will not be that much to be split into two subpages as stated in the analysis. Instead, these will be separate sections as follows:

|_Standards for Manual Testing
|__Tracking test cases
|___Rules
|___Testlink
|__Reporting bugs
|__Reviewing
|_Comments

The contents of these sections will be:

• Standards for manual testing - an overview of the contents of the page.
• Tracking test cases - rules for writing test cases; a how-to of using Testlink.
• Reporting bugs - how to report a bug in the Trac.
• Reviewing - what to look for when reviewing the test phase of a task.
• Comments - suggestions for improvements of the standards that will be used in the next revision.

Everyone has been asked about suggestions on the standards and the responses will be taken into consideration in the implementation.

A basic test plan should include at least:

• Opening Sophie2
• Creating/Opening a new book
• Adding/deleting pages to a book
• Adding/deleting frames on a page
• Saving/Closing books
• Closing Sophie2

These will be discussed with the Release team as a part of the implementation and will be expanded and added to Testlink. They will be run regularily as defined by the forthcoming standards.

Bug types custom field should be added to the Trac (with the help of pac). Bug types include, but are not limited to:

• data loss
• memory leak
• low performance
• regression (previously working feature is now broken),
• exception causing
• unexprected behaviour

In the implementation these will be discussed with the Release team and Milo to decide which to be added to a custom field in the Trac.

Implementation

^{(Implementation results should be described and linked here (from the wiki or the repository))}

Testing

Comments

^{(Write comments for this or later revisions here.)}