Changes between Version 9 and Version 10 of BluePrint/DestructiveTesting


Ignore:
Timestamp:
01/10/12 10:46:40 (13 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/DestructiveTesting

    v9 v10  
    2424  - explicitly state the impact on data integrity (e.g. "Record could not be deleted")
    2525  - where suitable, suggest what the user could do to
    26     a) mitigate the impact of the error (e.g. "Please contact the system administrator to ...")
    27     b) continue with the task the user was going to perform
     26    - mitigate the impact of the error (e.g. "Please contact the system administrator to ...")
     27    - continue with the task the user was going to perform
    2828
    2929This BluePrint shall document the procedures for a systematic destructive testing of a particular Eden module, with focus on "systematic", so that the testing covers as many possible user mistakes as possible, and in a way that the test cases can be easily reproduced for any Eden modules.