Summary
In this chapter, we went deeper into the high-level considerations frontend web application developers have when it comes to selecting a test automation framework.
As outlined in the chapter, there are a few generic considerations, such as ease of use and reporting, but also some specific requirements around test coverage, API and mock testing abilities, visual testing, and others that would vary from one project to another.
We provided a useful table that can be used as a baseline for a comparison of the various test automation frameworks.
Later in the book, in chapters 9-12, we will look into each of the capabilities (supported languages, community engagement, and so on) represented in the table, and provide a deep-dive analysis and comparison of each of these categories.
That concludes this chapter!
In the following chapter, we will advance the preceding test consideration matrix and provide a way to match each test automation framework with a testing methodology...