1# Release Testing 2 3**Last Update**: 2012-06-03 4 5This file describes the testing procedures that should be done when releasing 6Rocs. The test procedure starts with a simple checklist (that can be skipped 7by beta testers) and then focuses on testing the functional properties 8of the application 9 10## Release Checklist 11 12### Release Information 13 14* Application version is bumped 15* About Dialog is updated 16* Application information updated at edu.kde.org 17 18### Static Code Checkers 19 20* All (important) Krazy issues are fixed: 21 http://ebn.kde.org/krazy/reports/kde-4.x/kdeedu/rocs/index.html 22* Build issues are fixed: 23 https://build.kde.org/job/Applications/job/rocs/ 24 25### Unit Tests 26 27* All unit test pass: 28 https://build.kde.org/job/Applications/job/rocs/ 29 30### Documentation 31 32* Handbook builds 33* Handbook is updated 34 35### Website and Release Information 36 37* edu.kde.org is updated 38* features are correctly reported at KDE Feature List 39 40## Beta Test Instructions 41 42``` 43/////////////////////////////////////////////////////////////////////////////// 44Name of tester: 45Date: 46OS Version: 47Qt Version: 48KDE Version: 49/////////////////////////////////////////////////////////////////////////////// 50``` 51 52Before starting with the tests you should run the unit test to check whether 53your installation is fine. 54 55## Tutorial Tests / Documentation 56 57### T001 - Tutorial 58 59Test procedure: 60 611. Proceed steps as described in the Rocs tutorial in the handbook. 62 63### T002 - Compare UI elements from handbook with Rocs UI 64 65Test procedure: 66 671. Look up the User Interface Section in the handbook 682. Compare images and names of UI elements 69 70## Projects 71 72### P001 - Projectfiles 73 74Test procedure: 75 761. Create two data elements and connect them (data structure shall not be empty). 772. Write "test" into the script file. 783. Save project. 794. Close Rocs. 805. Open Rocs. 816. Load project. 82 83### P002 - Projectfiles with directory change 84 85Test procedure: 86 871. Create two data elements and connect them (data structure shall not be empty). 882. Write "test" into the script file. 893. Save project to folder foo. 904. Close Rocs. 915. Rename folder foo to baa. 926. Open Rocs. 937. Load project. 94 95### P003 - Export/Import (simple) 96 97Test procedure: 98 991. Create two data elements and connect them (data structure shall not be empty). 1002. Write "test" into the script file. 1013. Export project as archive. 1024. Close Rocs. 1035. Open Rocs. 1046. Import archive. 105 106### P004 - Export/Import with directory change 107 108Test procedure: 109 1101. Create two data elements and connect them (data structure shall not be empty). 1112. Write "test" into the script file. 1123. Export project as archive. 1134. Close Rocs. 1145. Move archive file to another folder. 1156. Open Rocs. 1167. Import project. 117 118## Create and Modify Data Structures 119 120## Script Engine 121 122## Script Execution 123