1. UI testing.
2. API testing.
3. Unit testing.
4. Other stuff (programming, test organization, framework and language, TDD).
It's not a book about libraries. It's more a book on technique. My goal here wasn't to teach anyone a particular library. It was to teach how to test, so the library wouldn't matter.
We use Ruby on Rails, RSpec, and Capybara. But it's not a book on those technologies. It's a book for testers who want to get into automation, and understand how testing frameworks work. And for programmers who want to get better at testing, with automation saving them a lot of time and making them more valuable to their teams.
Thanks for asking, Jonathan
get schwifty. tiny ad:
a bit of art, as a gift, that will fit in a stocking