Just reading the new chapter about Databases. It feels like a lot of effort to spend 6 pages refactoring the example from the previous chapter, rather than creating a simple standalone example. People might even choose to skip that previous chapter, since apps which use a databases tend to be more common than those which use a message queue.
Also, this really confused me:
“Capybara actually runs the web server in a separate thread within the same process, so you might think Cucumber and the web server share the same database connection. In fact they don’t—each thread also gets its own database connection, which means transactional cleaning won’t work. It obscures data from the other connection.”.
I’m pretty sure I’ve successfully used the Transaction approach with Rails/Capybara before. Isn’t that what the cucumber-rails generator defaults to?