Spec: Remove "todo" from Assertion event data

lib/Data.js

@@ -79,15 +79,13 @@ class Assertion {
    * @param {*} expected
    * @param {String} message
    * @param {String|undefined} stack
-   * @param {Boolean} todo
    */
-  constructor (passed, actual, expected, message, stack, todo) {
+  constructor (passed, actual, expected, message, stack) {
     this.passed = passed;
     this.actual = actual;
     this.expected = expected;
     this.message = message;
     this.stack = stack;
-    this.todo = todo;
   }
 }
 

spec/cri-draft.adoc

@@ -254,7 +254,6 @@ The **Assertion** object contains information about a single <<assertion>>.
 * `Mixed` **expected**: The expected value passed to the assertion, should be similar to `actual` for passed assertions.
 * `string` **message**: Name of the actual value, or description of what the assertion validates.
 * `string|undefined` **stack**: Optional stack trace. For a "passed" assertion, it is always `undefined`.
-* `boolean` **todo**: Whether this assertion was part of a todo test.
 
 It is allowed for additional non-standard properties to be added to am Assertion object, by the testing framework or a reporter.
 

test/integration/adapters.js

@@ -47,7 +47,7 @@ function normalizeTestEnd (test) {
     test.runtime = 42;
   }
 
-  // Only check the "passed" and any "todo" property.
+  // Only check the "passed" property.
   // Throw away the rest of the actual assertion objects as being framework-specific.
   if (test.assertions) {
     test.assertions.forEach(assertion => {