Changes between Version 7 and Version 8 of WebInspectorTests

Timestamp:

Aug 29, 2017 3:45:36 PM (7 years ago)

Author:

Nikita Vasilyev

Comment:

List assertion matchers. They are hard to find otherwise.

WebInspectorTests

@@ -67 +67 @@
 * Use `expectThat` instead of `assert` whenever possible. The former will always add output to the test, prefixing the condition with `PASS:` or `FAIL:`; the latter only produces output when the condition evaluates to false. Why should the default be to always log? For someone trying to understand how a test works or debug a failing test, the extra output is very helpful in understanding control flow.
 * Log runtime states sparingly, and only those that may help to diagnose a failing test. Logging runtime states can make tests more self-documenting at the expense of reducing robustness. For example, if a test logs source code locations, these could change (and cause the test to fail) if text is added to or removed from relevant file. It is better to assert actual output against known-good outputs. Don't dump runtime state that is machine-dependent.
+
+== Assertion Matchers
+{{{
+InspectorTest.expectThat
+InspectorTest.expectFalse
+InspectorTest.expectNull
+InspectorTest.expectNotNull
+InspectorTest.expectEqual
+InspectorTest.expectNotEqual
+InspectorTest.expectShallowEqual
+InspectorTest.expectNotShallowEqual
+InspectorTest.expectEqualWithAccuracy
+InspectorTest.expectLessThan
+InspectorTest.expectLessThanOrEqual
+InspectorTest.expectGreaterThan
+InspectorTest.expectGreaterThanOrEqual
+}}}
 
 == Important Test Fixtures