Posts

Showing posts with the label selenium

TA Basics: Test Framework on Linux (or VM)

Image
At some point I messed up my local test automation setup and I thought, maybe I should do the experimental things in a Virtual Machine. So here is a compact manual for a Ubuntu VM. For the VM I'm using the open source software VirtualBox from Oracle. There are plenty of manuals for that around on the internet. So I'm not going to cover how to install Virtual box with Ubuntu.  www.virtualbox.org But what I want to cover in this manual is an editor (Visual Studio Code), Ruby, a set of ruby gems (lapis_lazuli, Watir, Selenium-webdriver) and of course the webdriver itself (Geckodriver). So let's get started. Visual Studio Code installation Download the package from https://code.visualstudio.com/ I downloaded the 32bit debian version from https://code.visualstudio.com/docs/?dv=linux32_deb After that I followed the guide on https://code.visualstudio.com/docs/setup/linux sudo apt install ./<file>.deb Ruby + gems installation In the terminal: su...

TA: Who doesn't like proxies? Me!

Image
Are you on a company network that is using a proxy to connect to the internet? And do you want (or are you planning) to connect your tests to an external selenium-grid. Than stay tuned, before you get lost in a bunch of answers on the internet that don't resolve the issue you're facing. Source:  https://nl.wikipedia.org/wiki/Proxyserver I'm on a new project and looking into Robotframework. But then I bumped into an issue with the POC I had to make which might result in me convincing the company to switch to Ruby. Anyway long story short. They use a proxy and although the internet has all the answers, you do need to know what specific question to ask to get the correct result. And since proxies are not used that much anymore, it's hard to find the skilled people to help you out and push you in the right direction for a solution. The setup To access the internet, I need a configuration on my computer that will tell Windows to connect to a proxy server. I...

WTA with Ruby - A high level view of how it works

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...

Website Test Automation with Ruby - A Beginners Guide (blog forecast)

Image
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...