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.