Test Case Writing
Can this be done? I definitely asked myself this question when I started the challenge of only using the web client to accomplish my work
. The web client has an existing testing portal, and I can access both test cases and test runs. But, it doesn’t have the luxury of allowing me to open multiple windows at once. How can I write a new test case while consulting existing test cases and reviewing the functional requirement I am writing the test case from on the web client? I started asking around about this dilemma and a manager gave me a tip that would forever change my test case writing. To sum up that tip in one word: Reports.
“Ok, ok, ok, you’ve lost me now. I thought we were talking about writing test cases. And I can’t create reports on the web, can I?”, you must be asking yourself. Well I know, I thought the same thing! Here is where the web client’s power is realized. Yes, it’s true. I can’t view two windows at the same time in edit mode unless I use additional licenses and have multiple sessions open. But is this really needed? No.
Let me explain. I took a step back and looked at my process of writing test cases. Yes, I use several windows to do this. However, I only edit one item at a time. The requirement I am looking at is just a reference and the same goes for the test case I am comparing it to. I may copy and paste text from another item, but I am usually only editing one item at a time. Here is where the reports come in. Every item type has a reporting option on the Actions menu.
Specifically, I’ve found the <Item>DetailReport, <item>SummaryReport, and Requirement Document (for a full Specification Document Report) to be very helpful. I can generate reports for items I am going to compare and then I can generate the new test case from the requirement in my active TestTrack web session. When adding information and steps to the new test case, I can simply reference and even copy from the reports I generated. The reports can be additional tabs on my browser window or they can be a separate browser window that I reference on a second monitor.
This new method of writing test cases using the web client has worked so well, I’ve been able to use it for the past 150 test cases I’ve written without any issues related to time or lack of functionality! So the next time you find yourself settling down to write test cases, consider using this new method with the web client. I’m certain you will be surprised by the amount of functionality available.
Stay tuned for my next blog post regarding TestTrack Web navigation, as part 3 of the ‘TestTrack Web Challenge’! Are you ready?