Defect Scribe makes creating test cases with clear and consistent steps incredibly easy. In this short video, I'll show you how to record your test steps in Defect Scribe and turn that recorded script into a test case in Helix TCM (formerly TestTrack TCM). 
To get started, launch Defect Scribe and log in with your Helix TCM credentials. Once you've successfully logged into Defect Scribe, you need to configure the application under test. In this example, I'm going to verify that I can successfully login and create a new account within the Wysi CRM application. Once you've configured the application, click “Record” to begin the recording process. 
The first step in our test case is to log in as the sales user. Once logged in, we should see the accounts tab. 
The next step in our test case is to create a new account. And our contact at Mad Mike's is Mike. Now we hit “Tab” to make sure that this new account is saved. It looks like it was successful. We'll close the application and stop our recording. 
As you can see, Defect Scribe has taken my recorded actions and turned those into a step-by-step visual script of my test step. So, to make sure that our test case has a very clear, expected result, I want to go to the end of the test steps, and I'm going to annotate this last screenshot just to make it very clear to the tester what they should be seeing. 

I've done that quick annotation. I can now create my test case in Helix TCM. I elect my Helix TCM project and click “OK”. 
So now we're looking at the “Add Test Case” dialogue within Helix TCM. The first thing we'll do here is create a better summary description of our test case, and then we're going to review our test steps just to make sure that those are very clear and concise. The next thing we'll do here is pull out this information and actually copy/paste that over to the pre-conditions for this test case. And then we'll delete that comment from our steps. 

Okay, so first step here in the test case now is to select the edit box "User" and enter "Sales". And let's look at the screenshot. So, this screenshot is a visual representation for the tester of exactly what they should be doing in this test step. 

You can assume they know to press the “Tab” key or to click over to the password field. If you notice, it looks like the password field is actually called User 1. Let's clean that up to say password since that's what the tester will see when they're actually executing these test steps. Step three is to click the “Connect” button, which makes sense. 

Let's go down here to the very end and make sure that we have a very clear, expected result for this tester. You’ll notice that here's our screenshot that we annotated with the new account row. Let's change this step to more clearly outline the expected result. So, now we've made it very clear to the tester executing this test case what they should see when they decide whether to pass or fail this test case. We'll delete this final comment because it doesn't add much value to our test case. 

Looks like our test case is ready to go. We'll click “Add”, and we're finished. It's really that easy to create test cases with clear and concise steps using Defect Scribe. 

Thanks for watching. Learn more about Helix TCM >

Course - Using Defect Scribe