title: Necessary to use expect.assertions() if you're awaiting any async function calls?
body: <p>I've found a lot of this sort of thing when refactoring our Jest test suites:</p>
  
  <pre><code>it('calls the API and throws an error', async () =&gt; {
    expect.assertions(2);
    try {
      await login('email', 'password');
    } catch (error) {
      expect(error.name).toEqual('Unauthorized');
      expect(error.status).toEqual(401);
    }
  });
  </code></pre>
  
  <p>I believe the <code>expect.assertions(2)</code> line is redundant here, and can safely be removed, because we already <code>await</code> the async call to <code>login()</code>.</p>
  
  <p>Am I correct, or have I misunderstood how <code>expect.assertions</code> works?</p>