When I started my first QA job, it was my third career. At that point I had been in IT (with a side of document control) and a help desk technician was my second career. Each position taught me something about myself and dealing with people. I learned how to deal with angry people by being calm, how large companies handle desktop machines, and what 24/7 up time means on your personal life.
When I started working in Quality Assurance, automation was not the driving force that it is today. It was becoming common, but Test Driven Development was the goal of software companies. Unit testing was king. QA tested applications manually and focused on the user interface and experience. It wasn’t until my boss told me to look at WATIR that I began thinking about automation.
Software development is an industry that is always changing and reimagining itself, be it through disruptors in the Silicon Valley, startups in Colorado, or dreamers working from their home computers. The software industry is always in flux. Often, when a company looks to move from a traditional project planning release cycle to an Agile one, they immediately think of Scrum. This is natural as it is a buzzword, a word that is used in conversations without much discussion around it. As a result many individuals confuse Agile with a method. Surprisingly many business are looking for Agile Kanban, a process to push completed code out quickly, without the overhead of Scrum.
I have two test environments plus production and I need to run automation against them. What is the easiest way to configure your test automation to run against different site?
Today’s Code Snippet is for using a JSON configuration file with CapserJS and PhantomJS. I have been using JSON configuration files with my test automation for a while now to help manage test URLs, user agents, users, etc. It is a great way to make your automation more flexible and update settings for an entire application. Below is an example of how your configuration file would look.