Last week, I had a chance to review ( again..) some of the most popular automation testing tools in the market today.

Based on the my own research and reviews, I am no longer surprised that the free open source tools are still leading the popularity over the more expensive proprietary software from big named vendors.

I picked a couple of tools which were favorites mentioned in a a couple of QA forums. Then I came up with my own list, namely – JMeter, Selenium, Watir, C# and Java.

In this post, we will concentrate on one tool called Selenium.

Learning Selenium was a real breeze.

• First of all, there are so many sites dedicated on teaching the ins, outs and whys of Selenium.
• Second,  it is simple to use with an easy to navigate interface that comes as an Add On to the Firefox browser

Even if you are new to QA but if you have some technical knowledge, then within a day you would be creating your first few Selenium test cases.

My verdict : Selenium is really a good tool for testing web applications. It is free, and there is an excellent community of technical and non technical users who are willing to share their knowledge and expertise.

Instead of making this post too long, I would suggest you get started so you can try it for yourself.

From your Google Browser, just type the following words :

• First, “Selenium Tutorial”
• Or “Selenium Installation” to be more specific
• Then “Selenium Sample Test Cases”
• Or you can go to YouTube to watch videos like the one below

We’ll appreciate if you can also share your experiences in using Selenium!

Thanks.

Learning any new stuff always fascinates me. I never believe that anyone knows too much to quit learning.

Yesterday, I downloaded the demo version of the proprietary testing tool from ThoughtWorks called TWIST.  Within hours, I was already writing my own test projects and creating scenarios. What is amazing with TWIST is its capability to combine both manual test scenarios and the underlying automated script in one place. The BAs can write the use cases or use stories, then QAs and Developers can write the corresponding code to the same use cases minus the tedious and error prone linking steps. Gone would be the days when multiple, separate documents but referring to the same features are maintained by BA, QA and Developers.

When creating my first project, I tried using the Selenium driver since my background is testing web applications. Selenium’s unique  feature of record-and-replay can save the QAs large amount of time typing the code. Thou not all the steps can be automated, it still  speeds up code creation by the Selenium recorder.

Within the TWIST applications are also some very good testing tips on how to best create scenarios.  Its user friendly interface using simple plain text,  English-like constructs make the learning curve less steep.

Anyways, I am not here to sell TWIST, but I strongly suggest you give it a try is you are seriously thinking of automating your software projects.

What I really would like to share today are the higher level testing concepts I learned from TWIST.  Here they go :

• Separate the intent of the test from the mechanics of the test.
• Focus on what the test is suppose to do rather than how does the test work.
• Test scenarios should be independent of the user interface of the application.
• Test scenarios should strive to be at the highest level of abstraction possible, without sacrificing readabilty.
• Don’t repeat the tests: Repeating a series of steps at any level – at a scenario, or in the implementation can increase the maintenance overhead.

Based on my personal experience as QA, all of the above are true.  These are very simple yet neglected concepts in the testing world.  If you are a new tester, try to develop these correct thinking habits that would serve as your solid anchor in your long career.

I would trust that the above concepts are rather simple, but if you have questions feel free to leave a comment ot send me an email.