title: E2E Test Metrics
body: <p>Apologies if this question is better suited for Stack Exchange Programmers, I've posted this on both sites cause I figured it was on the fence.</p>
  
  <p><strong>Question:</strong> Are there any valuable metrics on E2E automated tests? (Does it make sense to gather any data around them?)</p>
  
  <p><strong>Context:</strong> For example, when I wrote my unit tests, I implemented a test coverage package which covers % of Classes, # of methods touched etc...</p>
  
  <p>A few points I've come across:</p>
  
  <ul>
  <li>Test efficiency (speed of specs)</li>
  <li>App performance (response/loading time)</li>
  <li>Automation Progress (# of tests currently automated VS # of tests able to be automated)</li>
  <li>Defect Efficiency (# of defects found during testing VS # of defects found after delivery)</li>
  </ul>
  
  <p>Any ideas?  If it matters, I'm using Protractor on an Angular app.</p>