In a recent team meeting, we discussed ways to increase our technological capacity. Currently, we have a fairly technical test team. Many of us are very good (or getting very good) at VB script, we have passable SQL skills, and possess a variety of backgrounds that include technical training and programming. As far as most test teams go, we are very technical, and we have the interest to take it further. The question is “where?”
One idea that came up was for us to learn another scripting language, such as Ruby or Python. The next thought, though, was what do we do with that knowledge? Hmm.
Using a scripting language with a testing library such as WATIR or Selenium, we can interact with web objects. Having the ability to interact with web objects and script test logic is a powerful thing. With this, you can write many utilities to assist with testing. These utilities do not have to be full-fledged, stand alone automation tools, but they are great levers for hybrid testing, tool-assisted manual testing.
But we have QTP (and presently, enough licenses). So what would Ruby or Python get us that we don’t already have? Here a couple thoughts in no particular order:
* Technical prestige. VB Script is a great tool, but it doesn’t get as much respect as other languages. Jerks.
* License extender. If you use Ruby or Python for day-to-day tasks, you do not tie up expensive QTP licenses.
* Professional growth. Learning and using open-source tools enables you to evaluate different tools and to participate in more industry discussions.
* An open mind. Learning how to perform a task using different tools opens you to different approaches to other things.
* Interaction with the open-source community. Becoming proficient with these tools may give you an opportunity to give back.
Now, we need to find the time to learn Ruby (or Python)