Skip to end of banner
Go to start of banner

UI Testing Tool Evaluation Criteria 

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

  1. Speed

  2. Reliability

  3. Relevance

  4. Mocking facility (Mirage - mocking HTTP requests)

  5. Cost to migrate/rebuild existing tests

  6. Multi browser support

  7. Parallel  Execution (not for e-2-e tests)

  8. Coverage collection 

    1. Istanbul for Unit and Integration tests

    2. reportportal.io or testrail.io for e-2-e test

  9. Open Source Community Support



CypressJestEnzyme

Speed6



Reliability10



Mocking?



MigrationI know from browsing the documentation that there are facilities for providing mocks, and in particular data fixtures seem well supported, but I have not used any of this.



Multi-browser8



|| executionI know that there is support for this, but I have not attempted to use it because so many of my tests involve making changes to the data (adding and editing courses, instructors and reserves) that they are not even in principle parallelizable.



Coverage10



Community10



Extras




  • No labels