The more I use Rake for automation of our testing process, the more I like it. Where I work, we have a Java-based web application. However, I have found that using Rake, not Ant, is definitely the tool of choice for automating the configuration and running of our QA tests. Here are some of the reasons:
- Rake uses Ruby scripts as their ‘rakefile’ – Ant uses XML files, which are great for storing structured data but have no real ability to perform logic or make decisions. Rake, on the other hand, uses actual Ruby syntax within their ‘rakefile’, which means you have full access to the Ruby ecosystem. This allows you to utilize decision structures, closures, even classes if you desire.
- Rake is fully supported by Intellij and TeamCity – I am not sure what Rake’s support is in other environments, but our development/automation environment is Jetbrains’ Intellij for the IDE and TeamCity for the build automation. Both have terrific support for Ruby and Rake.
- Rake has great support for RSpec – RSpec is our test framework…and Rake has great support for it.
Some of our tests in the future might be Jython tests run from the server (under the JVM), but they can still be easily launched from a Ruby/RSpec script (via a web services API). This is ideal, because it gives us the best of both worlds…the ability to quickly script tests through Ruby when possible, but also the ability to access the product’s underlying classes when we need to.
No comments:
Post a Comment