title: expect() with no actual expectations
body: <p><strong>The Problem:</strong></p>
  
  <p>Recently, while reviewing our existing test codebase, I've noticed a dangerous kind of typo/mistake when <code>expect()</code> was used without the "matching" part:</p>
  
  <pre><code>expect(page.filters.fromDateLabel.getText(), "After");
  </code></pre>
  
  <p>I'm pretty sure <code>toEqual()</code> was meant to be used here:</p>
  
  <pre><code>expect(page.filters.fromDateLabel.getText()).toEqual("After");
  </code></pre>
  
  <p>The problem with this is that <code>jasmine</code> would not fail the expectation in this case (well, obviously because nothing was actually expected). And this gets us to a more serious problem - nothing was actually tested in a test case - it was passing with no expectations made. We were getting a false sense of what was tested.</p>
  
  <p><strong>The Question:</strong></p>
  
  <p>I want to catch these mistakes as fast as possible. How do you think I should handle the problem?</p>
  
  <p><strong>Thoughts:</strong></p>
  
  <ul>
  <li>somehow fail a test case if there was no expectations made in it (not sure if <code>jasmine</code> has anything like this built-in)</li>
  <li>"patch" the <code>expect()</code> and issue a warning/raise an error if nothing was called on the "expect" part</li>
  <li>use static code analysis - define a custom <a href="http://eslint.org/"><code>eslint</code></a> rule</li>
  </ul>