[[BackLinksMenu]]

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

= Analysis =

== Overview ==

== Task requirements ==
Update and revise PLATFORM_STANDARDS_MANUAL_TESTS
 * Update [wiki: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 [wiki:PLATFORM_STANDARDS_MANUAL_TESTS] and [http://sophie2.org/testlink 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:
 * 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:
[BR]On every iteration these are the basic test plan steps 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.||

In the progress of testing, this plan will be expanded and more test plans will be added. 
  
Reporting Bugs:

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

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, .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 =
^(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.)