Explore >> Select a destination
|
You are here 
|
chriskottom.com | ||
| | | | |
martinfowler.com
|
|
| | | | | Find out what kinds of automated tests you should implement for your application and learn by examples what these tests could look like. | |
| | | | |
nikoheikkila.fi
|
|
| | | | | How can we improve the developer experience in writing tedious browser-based tests? | |
| | | | |
janko.io
|
|
| | | | | When I joined my current company, the system tests for our Rails app used Selenium as the Capybara driver. I didn't have good experiences with Selenium in the past, mostly it was tedious to have to keep chromedriver up-to-date with the auto-updating Chrome. In this project, I was frequently hitting maximum number of open file descriptors on my OS when running system tests, probably in combination with Spring. We're using the Webdrivers gem, and we also needed to ignore its download URLs in VCR and WebMoc... | |
| | | | |
www.raygervais.ca
|
|
| | | Or at least, that's what we all think at the start of the project. Every code-base has their respective hacks, workarounds, and inconsistencies when not kept in check. I imagine that consistent code quality in each pull request is the goal, but we all know how easy it is for items to slip past our reviews. That's why I wanted to explore adding Code Analysis tooling from the very start to the project for both the front-end and back-end. Enter the first tool, Hound! | ||
