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 PLATFORM_STANDARDS_MANUAL_TESTS with the comments from the previous release
• Resources used for the zip file must have the proper licence (with Creative Commons-licensed content)

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

• Image files
• Audio files
• Video files
• HTML
• PDF
• Script
• A book for embedding with all supported resources
• Make sure all the names in the file are all-platforms friendly. See ​http://en.wikipedia.org/wiki/Filename#Comparison_of_file_name_limitations

Discuss with the integrators whether to put the zip file in the second refactoring branch or only in the trunk.

Task result

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

Implementation idea

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

• Improve the Testcases, Reporting Bugs and Rules and Scoring of Reviewing sections of PLATFORM_STANDARDS_MANUAL_TESTS

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!" should be revised.
• Unnesesary highlights such as "Non-integer scores are STRONGLY disencouraged." will be changed to lowercase letters.

TestCases:

• 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.

For NewTestResources.zip

• for the zip add large-, medium- and small-sized picture resources
• all the files added to the zip file should be Creative Commons-licensed content for commercial use
• find files for all the common file types for testing
  • for video - ​http://www.fileinfo.com/filetypes/video
  • for audio - ​http://www.fileinfo.com/filetypes/audio
  • for images - ​http://www.fileinfo.com/filetypes/image
• the owners of the used resources must be notified that we use their files and noted in the documentation of the TestResourses

Related

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. A list of file types included in NewTestResources.zip is provided.

TestCases:

On every iteration these are the basic testplan cases that should be executed and that should always work:

Testcase:	Expected Results:
Start Sophie2.	Sophie2 should start in default skin with open left, bottom and right flap.
Create a new book.	A new book should be created.
Add a page to the book.	A new page should be added to the book.
Add a resource frame to a page of the book.	A resource frame is added to the page.
Delete a frame from a page in the book.	The wanted frame is deleted from the page.
Delete a page from the book.	The wanted page is deleted from the book.
Save the book.	The book is saved.
Close the book.	The book is closed.
Open an existing book.	The book is loaded.
Exit Sophie2 .	Sophie2 is closed.

All testcases must

• begin with either one of these choices:

Steps:	Expected Results:
1. Start Sophie2.	1. Sophie2 should start in default skin with open left, bottom and right flap.
2. Create a new book.	2. A new book should be created.

or

Steps:	Expected Results:
1. Start Sophie2.	1. Sophie2 should start in default skin with open left, bottom and right flap.
2. Open an existing book.	2. The book is loaded.

and end with these steps:

Steps:	Expected Results:
...	...
8. Save the book.	8. The book is saved with all the made changes.
9. Close the book.	9. The book is closed.
10. Open the saved book.	10. The book should load with all the made changes before saving.

There is no limit to the number of steps in a testcase. In the progress of developing the project different testplans will be added depending on the various expectations towards the testplan results.

Reporting Bugs:

Analysis of Bugs:

• If a bug is a TLID type it must be clarified in the comment of the ticket on which step the application crashes.
• In Design and Implementation the attachments must be linked properly if mentioned.
• It is recommended that the attachments' names do not have spaces or any special symbols because you might 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. If you give the testing a score of 3.5, then you probably have not reviewed it thoroughly enough and cannot clearly state whether it is good or not." is changed to
  • "Scores should be in the range from 1 to 5 with a recommended step 1. A 0.5 step is also possible but if you give the testing a score of 3.5 then you probably have not reviewed it thoroughly enough and cannot clearly state whether it is good or not. Integer numbers are recommended."

All of these changes applied in PLATFORM_STANDARDS_MANUAL_TESTS_R3/Design

Most common files for the zip file:

• for video - .mov, .avi, .flv, .mp4, .mpg, .mpeg, .swf, .wmv, .mkv, .3gp, .3g2, .asf, .asx
• for audio - .wav, .mp3, .cda, .wma, .mid, .midi, .ogg, .amr, .mp2, .mpa, .aac, .aif, .aiff
• for images - .jpg, .jpeg, .bmp, .gif, .png, .tif, .tiff
  • for the images there is a small, medium and large version for testing

Implementation

• PLATFORM_STANDARDS_MANUAL_TESTS_R3/Design is created
• PLATFORM_STANDARDS_MANUAL_TESTS/Bugs is updated
• PLATFORM_STANDARDS_MANUAL_TESTS is updated with the content of PLATFORM_STANDARDS_MANUAL_TESTS_R3/Design
• Attached NewTestResources.zip consisting of file types:
  • audio - .wav
  • images - .jpg, .jpeg, .bmp, .gif, .png, .tif, .tiff
  • video - .mov, .avi, .mp4, .mpg .3gp
  • usedResources.txt - a text file containing references to the used resources
• Attached NewTestResourcesSpaces.zip consisting of same files as NewTestResources.zip but with spaces in their names
• Not supported file types up to the moment of uploading NewTestResources:
  • audio -
  • image -
  • video -

Testing

^{(Place the testing results here.)}

Comments

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