Changes between Version 84 and Version 85 of Event/2011/GCI
- Timestamp:
- 11/21/11 06:52:01 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Event/2011/GCI
v84 v85 9 9 === Fixing Bugs === 10 10 '''''Migrated'''''[[br]] 11 ==== Hard: http://eden.sahanafoundation.org/report/1 ==== 11 ==== Hard ==== 12 http://eden.sahanafoundation.org/report/1 12 13 Pick a bug report from http://eden.sahanafoundation.org/report/1, try to reproduce the issue in a local instance, fix the problem and submit a patch to the ticket on Trac, then notify the Sahana-Eden mailing list about your patch for verification. 13 ==== Medium: http://eden.sahanafoundation.org/report/18 ==== 14 ==== Medium ==== 15 http://eden.sahanafoundation.org/report/18 14 16 Pick a bug report from http://eden.sahanafoundation.org/report/18, try to reproduce the issue in a local instance, fix the problem and submit a patch to the ticket on Trac, then notify the Sahana-Eden mailing list about your patch for verification. 15 17 … … 157 159 158 160 == '''Quality Assurance''' == 159 * 2 xTesting and reporting bugs 160 '''''Not migrated'''''[[br]] 161 * Using Selenium IDE create test scripts for an application see: http://eden.sahanafoundation.org/ticket/1035 (medium) '''''Not migrated'''''[[br]] 161 === Report 2 Bugs in Sahana Eden === 162 Following http://eden.sahanafoundation.org/wiki/BugReportingGuidelines 163 '''''Migrated''''' 164 165 === Destructive testing of a Sahana Eden module === 166 Test the forms and screens of a Sahana Eden module for appropriate/consistent response to user errors (e.g. invalid or malformed input, accidental navigation actions, invalid URL, etc...). Document all the steps that you've taken and report any bugs you've found in the process. 167 '''''Migrated''''' 168 169 === Develop a test cases for a Sahana Eden module === 170 Write up the steps to perform the user tasks in the module, automate the tests using Selenium IDE, provide test data where useful. 171 '''''Migrated''''' 172 173 === Test a Sahana Eden module for correct access authorization === 174 Find out and document the common business rules for access authorization to the module, test the module for the consistent implementation of these rules and document the results 175 '''''Migrated''''' 176 177 === Create a Selenium IDE script for a Sahana Eden application === 178 Using Selenium IDE create test scripts for a module see: http://eden.sahanafoundation.org/ticket/1035 (hard) 179 '''''Migrated''''' 162 180 163 181 == '''Research''' == 164 === Create disaster scenarios & demos with data through pre-populate === 165 '''''Not migrated'''''[[br]] 166 The objective is to collect real or at least realistic data which can be used to illustrate some of the capabilities of Sahana Eden. The task requires a little research on the disaster risk reduction, preparedness and response capabilities in your location. 167 168 You will need to collect some data and save them in a format that can be imported directly into Sahana Eden. This will be achieved by creating a number of CVS files and conforming strictly to the format described in each file. 182 === Create A Disaster Scenarios === 183 The objective is to collect real or at least realistic data which can be used to demonstrate some of the capabilities of Sahana Eden. The task requires a little research on the disaster risk reduction, preparedness and response capabilities in your location. 184 185 You will need to collect some data and save them in a format that can be imported directly into Sahana Eden through the Pre-Populate functionality. This will be achieved by creating a number of CVS files and conforming strictly to the format described in each file. 169 186 170 187 Note: When adding personal information it is essential that the data have been modified such that it can not be used to identify any real person. As a general rule all email addresses should be from the example.com domain, thus the email address for Joe Bloggs might be joe.bloggs@example.com, phone numbers should look realistic but should not be true numbers. … … 180 197 Template file are held in the attached archive file "research disaster scenario.zip" 181 198 182 Easy 199 ==== Easy ==== 183 200 ||=Type of resource =||= Number of entries =||= File =|| 184 201 || Organisation || 3||org/organisation.csv || … … 187 204 || Staff || 50|| hrm/person.csv || 188 205 The recommended means of testing for this task is, to successfully open as a spreadsheet file, but saved as a CSV file, however if the student is able to set it up in a pre-populate folder that will make up for any significant shortfall in the entries. 206 '''''Migrated''''' 189 207 190 208 Medium … … 198 216 || Stock || 120|| inv/inv_item.csv || 199 217 The recommended means of testing for this task is, attempt to import the data into eden using the menus. However if the student is encouraged to try and set it up in a pre-populate folder. 218 '''''Migrated''''' 200 219 201 220 Hard … … 209 228 || Stock || 120|| inv/inv_item.csv || 210 229 || Request for stock items || 120|| req/req.csv || 230 '''''Migrated''''' 211 231 212 232 The recommended means of testing for this task is, attempt to import the data in a pre-populate folder. The data must be delivered in a single folder suitable for pre-populate even if the student was unable to run the pre-populate task. 233 213 234 === Map elements between EDXL-SITREP and EDXL-RM === 214 235 '''''Migrated'''''[[br]]