A Test Automation Blog

You're most likely already familiar with manual testing and different tools and techniques, but manual testing (especially when done repetitive) becomes a very boring task very quick. Also it might be way more efficient to use test automation for repetitive tasks or the ones that are difficult to perform manually. So you want to look into test automation. What do you do? Where do you start? Scripting/Programming Language There are so many tools and languages to use that it's difficult to choose. Usually you start with what is already available in your company, or something that makes sense to use for your project. But if you can start from scratch and there is nothing available in your company and you have no preference for any programming/scripting language, why not start with Ruby . In my experience it was fairly easy to get used to, without to much programming knowledge. Tools Then there is still the task to choose a tool to script for. For website test automation t

The past During my time at spriteCloud I got my first experience with Test Automation. A crash course in test automation and some days later, I started to write some Gherkin scenario's and test scripts for my own project. SpriteCloud developed a Ruby gem called lapis_lazuli. If you're not familiar with Ruby, it's a plug-in/add-on/extension. This lapis_lazuli gem makes life easier especially for beginners, but I'll explain more about that in one of the next blog posts. The present These days I work for Mproof  to test their new product called Service-Hub . And I'm no test automation master (yet), but I've gained quiet some experience by now and are quiet familiar with the Ruby + Cucumber combination. Still almost every day I learn something new. So I thought it would be nice to share. For you and for me Since the internet is a bit of a jungle of information. You will easily loose time researching an issue that has already been encountered/resolved be