How do I create test cases in ReQtest?
You have two options when creating test cases.
You can either click on the top icon which says ‘create new test case’ or you can click on ‘plan test’ and ‘create test case’ after.
You’ll get a template that needs to be filled out on your screen. This template can be configured to better fit your project’s needs, and we have videos explaining how to do that here.
Let’s assume that I’m testing a discussion board on the web, and this specific test case is going to be about blocking users on my discussion board.
You will obviously need a title for the test case. Choose something short, clear and descriptive enough so that the tester can quickly discern what the test case is all about when going through a large list of test cases.
Click the ‘Subsystem’ drop down to bring up the section of the system the test case is concerned with. I’ve prepared a number of different subsystems but this particular test case will go to administration.
Select the type of test case, so whether this is a functionality issue, performance or anything else.
The preconditions field is useful to write information or instructions in, for instance if you want the tester to use a specific version of the system that is being testing.
Below the preconditions field you will find to two drop down menus. The first is the test case’s review status, and the second one is to select an auditor for the test case, so that they can review it before the tester actually executes test cases.
In a test case you will typically have more than one step. To add new steps in a test case, simply click on the little green plus icon beneath the Step 1 text. Of course, each and every step must have a description and an expected result. My steps and expected results are, for example;
Step1: Log in as an administrator
Step2: Go to the admin page, select the user and click ‘block’
Expected result is that the user is marked as blocked
Step 3: Log out. If you try to log in as the user you’ve blocked, the expected result is you’re not logged in. A message is shown saying that the account has been blocked.
What’s described above is pretty much a typical test case. When you’re done, click the blue ‘save’ button at the bottom of the screen. You’ll get a message at the top of the page saying that the test case has been saved.
When you save a test case you will go back to the ‘view’ mode, in which you can see the information that you’ve just filled in. Here you can see what we call the execution results. Since this a new test case it automatically gets a ‘not run’ status. If this test case had already been run and failed, this would’ve been red instead of grey.
Up at the top of the page are a couple of new and very useful tabs. In the ‘Attached files’ section you can attach any type of file to the test case; be it an Excel file or a Word file containing test data to the specific test case or even a screen capture which you can make using our integrated tool, ReQtest Snapshot.
In the history tab you can follow exactly what has happened to the test case, from the date and time of when the test case was created onward. Again, given this is a new test case, the only thing you will have is the date and time at which the user created the test case, and who the user was.
Sometimes when you’re writing text cases they can be quite similar. This is why we created the ‘create copy’ function. This basically makes an exact copy of the test case I just created in which I can make minor changes, such as change the content of the test case. Of course, when you save it, the new test case gets its own unique ID. This way you save a lot of time; instead of re-writing the test case altogether, you simple make the smaller changes needed.
Click ‘view all test cases’ to get a list of all your test cases in your specific project.
Writing and creating new test cases in ReQtest is extremely easy and simple. The video below explains everything written above too!
Join 60,000+ Subscribers
For latest blogs, industry updates and exclusive tips.
*Your email is safe with us, we also hate spam