wiki:PLATFORM_STANDARDS_MANUAL_TESTS_R3

Version 12 (modified by vanya, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=PLATFORM_STANDARDS_MANUAL_TESTS_R3, 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

Task requirements

Update and revise PLATFORM_STANDARDS_MANUAL_TESTS

Update the zip in the repository with all of the supported frame contents for manual and auto tests.

  • Supported image files
  • Supported audio files
  • Supported video files
  • HTML
  • PDF
  • Script
  • A book with all resources (embedded book too) and add it to the zip for embedding.
  • All of these with exotic filenames. See ​http://en.wikipedia.org/wiki/Filename#Comparison_of_file_name_limitations
  • Link the zip in the integration page Integration
  • Decide whether to put the zip file in the second refactoring branch or only in the trunk
  • add large and small versions of the files for better testing of the application

Task result

  • Updated wiki page linked where needed
  • Updated zip file with the supported resources

Implementation idea

See previous revisions PLATFORM_STANDARDS_MANUAL_TESTS, Testlink and Bugs page. Discuss with integrators.

  • for the zip add large- and small-sized resources

PLATFORM_STANDARDS_MANUAL_TESTS all revisions.

How to demo

Show the updated standarts and zipped resources.

Design

Comments from PLATFORM_STANDARDS_MANUAL_TESTS will be executed:

  • Test cases may contain clearly defined prerequisites - only one in between creating or opening a new book must be the chosen step in every test case.
  • All test cases must end with steps: "Save the book." and "Load the book." and in case needed - a last step to show that the changes made to the book are saved in it.
  • "When writing manual tests, do not forget the general guideline of the project: Work towards the goal!" will be revised as "When writing manual tests, keep in mind the general guideline of the project!".
  • Unnesesary highlights such as "Non-integer scores are STRONGLY disencouraged." will be changed to lowercase letters.

TestCases:

  • a link to Sophie2's Testlink will be added to the wiki page - http://sophie2.org/testlink/
  • revise the basic rules of writing testcases
    • make sure there is only one choice for starting a book in a testcase - "Open Book" or "Create new book"
    • test cases cannot be limited to "up to 15 steps" if we want the steps to be simple and sigle-actioned
    • in the basic test plan example steps should be separated
    • It should be clarified that some testcases might have to have different substeps or steps inside them for the different skins

Reporting Bugs:

  • In Analysis of Bugs:
    • if a bug is a TLID type it must be clarified on which step the application crashes
  • In Design and Implementation the attachments must be linked properly if mentioned.
  • The attachments' names shouldn't have spaces because you will not be able to link them properly in the ticket.
  • Test: Test is performed by the reporter or in some needed cases by an integrator. If the bug is not present the ticket is closed.

Reviewing:

  • Rules
    • Links to the needed attachments for testing should be provided
  • Scoring
    • "Non-integer scores are STRONGLY disencouraged" will be changed to "Scores should be from 1 to 5 with a minimum of 0.5 step. Integer numbers are recommended."

Implementation

(Describe and link the implementation results here (from the wiki or the repository).)

Testing

(Place the testing results here.)

Comments

(Write comments for this or later revisions here.)