94. I test them using the FAILURE mnemonic v1.2 FAILURE.QualityFrog.com
95. A mnemonic is a device that aids memory recall v1.2 FAILURE.QualityFrog.com
96. The FAILURE mnemonic is an acronym that helps me recall guideword heuristics v1.2 FAILURE.QualityFrog.com
97. Guideword heuristics are words that guide thinking through a problem v1.2 FAILURE.QualityFrog.com
98. The FAILURE mnemonic’s guideword heuristics help me think about testing error messages v1.2 FAILURE.QualityFrog.com
99. The F reminds me to think about Functional aspects of the error F AILURE v1.2 FAILURE.QualityFrog.com
100. I ask Functional questions like Does the error detection function as expected? v1.2 FAILURE.QualityFrog.com
101. I ask Functional questions like Does the error handling function as expected? v1.2 FAILURE.QualityFrog.com
102. I ask Functional questions like Does the error reporting function as expected? v1.2 FAILURE.QualityFrog.com
103. I ask Functional questions like Does the error dialog, window, or page function as expected? v1.2 FAILURE.QualityFrog.com
104. I ask Functional questions like Does the software recover from the error? v1.2 FAILURE.QualityFrog.com
105. I ask Functional questions like Was there really an error? v1.2 FAILURE.QualityFrog.com
106. I ask Functional questions like Are other errors like this reported? v1.2 FAILURE.QualityFrog.com
107. I ask Functional questions like Do dialog buttons work? v1.2 FAILURE.QualityFrog.com
108. I ask Functional questions like Is error message information accurate? v1.2 FAILURE.QualityFrog.com
109. I ask Functional questions like Is it functional? v1.2 FAILURE.QualityFrog.com
110. Only I don’t stop at Functional v1.2 FAILURE.QualityFrog.com
111. A Functional error message is not necessarily an Appropriate error message v1.2 FAILURE.QualityFrog.com
112. The A reminds me to ask if the error reporting is Appropriate F A ILURE v1.2 FAILURE.QualityFrog.com
113. I ask Appropriate questions like Is the error reporting timely? v1.2 FAILURE.QualityFrog.com
114. I ask Appropriate questions like Is the error reporting accurate? v1.2 FAILURE.QualityFrog.com
115. I ask Appropriate questions like Are UI messages free of inappropriate technical detail? v1.2 FAILURE.QualityFrog.com
116. I ask Appropriate questions like Is there a better way to handle or report the error? v1.2 FAILURE.QualityFrog.com
117. I ask Appropriate questions like Is the error user friendly? v1.2 FAILURE.QualityFrog.com
118. I ask Appropriate questions like Are errors detected as early in the user workflow as possible? v1.2 FAILURE.QualityFrog.com
119. I ask Appropriate questions like Are system resource problems detected while there is still time to remedy the problem? v1.2 FAILURE.QualityFrog.com
120. I ask Appropriate questions like Is the situation communicated appropriately for the intended audience? v1.2 FAILURE.QualityFrog.com
121. I ask Appropriate questions like Is a user allowed to waste time and effort only to be told that their work cannot be applied? v1.2 FAILURE.QualityFrog.com
122. The I reminds me to ask about the Impact of the error FA I LURE v1.2 FAILURE.QualityFrog.com
123.
124.
125.
126. I ask Impact questions like Will the user understand the impact? v1.2 FAILURE.QualityFrog.com
127.
128. I ask Impact questions like Does the message contain too much information? v1.2 FAILURE.QualityFrog.com
129.
130. The L reminds me to ask about the error Log FAI L URE v1.2 FAILURE.QualityFrog.com
131. I ask Log questions like Should the error be logged for support? v1.2 FAILURE.QualityFrog.com
132. I ask Log questions like Should the error be logged for system administrators? v1.2 FAILURE.QualityFrog.com
133. I ask Log questions like Should the error be logged for developers? v1.2 FAILURE.QualityFrog.com
134. I ask Log questions like Should the error be logged for technical investigation? v1.2 FAILURE.QualityFrog.com
135. I ask Log questions like Will log information be available if the user waits to report a problem? v1.2 FAILURE.QualityFrog.com
136. I ask Log questions like Are log messages standardized to support automated information mining? v1.2 FAILURE.QualityFrog.com
137. I ask Log questions like Can I grep this error? v1.2 FAILURE.QualityFrog.com
138. I ask Log questions like Do logs contain enough information? v1.2 FAILURE.QualityFrog.com
139. I ask Log questions like Do logs contain useless information? v1.2 FAILURE.QualityFrog.com
140.
141.
142.
143.
144.
145. The U reminds me to think about the User Interface FAIL U RE v1.2 FAILURE.QualityFrog.com
146. I ask UI questions like Is the error reported to the user? v1.2 FAILURE.QualityFrog.com
147. I ask UI questions like Does this error need to be reported to the user? v1.2 FAILURE.QualityFrog.com
148. I ask UI questions like What user activity caused the failure? v1.2 FAILURE.QualityFrog.com
149. I ask UI questions like What user activity caused the failure? Is this communicated to the user? v1.2 FAILURE.QualityFrog.com
150. I ask UI questions like Who is the user? v1.2 FAILURE.QualityFrog.com
151. I ask UI questions like Are UI messages worded for the intended audience? v1.2 FAILURE.QualityFrog.com
152. I ask UI questions like Is this message consistent with the desired look and feel? v1.2 FAILURE.QualityFrog.com
153. I ask UI questions like Is the UI reporting consistent with reporting for other errors? v1.2 FAILURE.QualityFrog.com
154. I ask UI questions like Is the UI reporting efficient? v1.2 FAILURE.QualityFrog.com
155. I ask UI questions like Does the user need to click away excessive dialogs? v1.2 FAILURE.QualityFrog.com
156. I ask UI questions like Is this the best way to communicate the error? v1.2 FAILURE.QualityFrog.com
157. I ask UI questions like Could this error be handled without involving the user? v1.2 FAILURE.QualityFrog.com
158. The R helps me think about error Recovery FAILU R E v1.2 FAILURE.QualityFrog.com
159. I ask Recovery questions like Is the user told how to recover from the impact of the error? v1.2 FAILURE.QualityFrog.com
160. I ask Recovery questions like Does the user need to contact support? v1.2 FAILURE.QualityFrog.com
161. I ask Recovery questions like Is support contact information provided? v1.2 FAILURE.QualityFrog.com
162. I ask Recovery questions like Does support know how to fix the problem? v1.2 FAILURE.QualityFrog.com
163. I ask Recovery questions like Does the software guide the user through the recovery process? v1.2 FAILURE.QualityFrog.com
164. I ask Recovery questions like Or is the user left to figure it out on their own? v1.2 FAILURE.QualityFrog.com
165. The E leads me to think about the Emotions of users FAILUR E v1.2 FAILURE.QualityFrog.com
166. I ask Emotions questions like What emotions are likely to be raised by the error message? v1.2 FAILURE.QualityFrog.com
167. I ask Emotions questions like Does the error reporting evoke the desired user emotions? v1.2 FAILURE.QualityFrog.com
168. I ask Emotions questions like Does this message enhance user frustration? v1.2 FAILURE.QualityFrog.com
169. I ask Emotions questions like Does this message quiet user frustration? v1.2 FAILURE.QualityFrog.com
170. I ask Emotions questions like Does this message encourage users to use some other product? v1.2 FAILURE.QualityFrog.com
171. I ask Emotions questions like Does this message cause confusion? v1.2 FAILURE.QualityFrog.com
172. Asking these types of questions can help turn FAILURE into success v1.2 FAILURE.QualityFrog.com
173. The next time you encounter an error message v1.2 FAILURE.QualityFrog.com
174. The next time you encounter an error message Test it! v1.2 FAILURE.QualityFrog.com
175. The next time you encounter an error message Question it! v1.2 FAILURE.QualityFrog.com
176.
177. And let me know how it works for you v1.2 FAILURE.QualityFrog.com F unctional A ppropriate I mpact L og U I R ecovery E motions
