Having a suite testing a lot of features is a good thing. But if your project supports a lot of different Rubies – MRI-Ruby, JRuby etc. – you might face platform dependent bugs. Read on, if you like to know how we worked around some platform dependent bugs in aruba to keep the build status “green” on all support Rubies.
Some of my rubygems – e.g. proxy_pac_rb – either need a backing HTTP(S)-server for their tests or interact with some external web services via HTTP/HTTPS. To mock external services you can either use VCR, webmock or just plain Webrick. To serve data for your tests via HTTP(S), you can use Webrick as well. As Webrick is part of ruby core and is sufficient for both use cases, this article only describes ways to run a Webrick-HTTP(S)-server to back your test suite.
