OLD | NEW |
1 // Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file | 1 // Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file |
2 // for details. All rights reserved. Use of this source code is governed by a | 2 // for details. All rights reserved. Use of this source code is governed by a |
3 // BSD-style license that can be found in the LICENSE file. | 3 // BSD-style license that can be found in the LICENSE file. |
4 | 4 |
5 part of matcher; | 5 part of unittest.matcher; |
6 | 6 |
7 // To decouple the reporting of errors, and allow for extensibility of | 7 // To decouple the reporting of errors, and allow for extensibility of |
8 // matchers, we make use of some interfaces. | 8 // matchers, we make use of some interfaces. |
9 | 9 |
10 /** | 10 /** |
11 * The ErrorFormatter type is used for functions that | 11 * The ErrorFormatter type is used for functions that |
12 * can be used to build up error reports upon [expect] failures. | 12 * can be used to build up error reports upon [expect] failures. |
13 * There is one built-in implementation ([defaultErrorFormatter]) | 13 * There is one built-in implementation ([defaultErrorFormatter]) |
14 * which is used by the default failure handler. If the failure handler | 14 * which is used by the default failure handler. If the failure handler |
15 * is replaced it may be desirable to replace the [stringDescription] | 15 * is replaced it may be desirable to replace the [stringDescription] |
(...skipping 79 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
95 * the [reason] (argument from [expect]), some additonal [matchState] | 95 * the [reason] (argument from [expect]), some additonal [matchState] |
96 * generated by the [matcher], and a verbose flag which controls in | 96 * generated by the [matcher], and a verbose flag which controls in |
97 * some cases how much [matchState] information is used. It will use | 97 * some cases how much [matchState] information is used. It will use |
98 * these to create a detailed error message (typically by calling | 98 * these to create a detailed error message (typically by calling |
99 * an [ErrorFormatter]) and then call [fail] with this message. | 99 * an [ErrorFormatter]) and then call [fail] with this message. |
100 */ | 100 */ |
101 void failMatch(actual, Matcher matcher, String reason, | 101 void failMatch(actual, Matcher matcher, String reason, |
102 Map matchState, bool verbose); | 102 Map matchState, bool verbose); |
103 } | 103 } |
104 | 104 |
OLD | NEW |