Fundamentals of Writing Good Test Cases

It doesn ’ t matter how well-designed a sure package is, it needs to go through multiple stratum of testing before liberation. Hence, every tester or QA has to write multiple test cases in every project they are involved with.

Naturally, writing good examination lawsuit is of extreme grandness. This article aims to help reader with exactly that.

Let ’ s begin with examining the characteristics of a good test case:

• Stand in the client ’ s shoes

It is not uncommon for customers to call support staff in order to kvetch that a certain application feature is perform below expectations. Any tester must be capable to relate to customers, foreknow their needs and make examination cases consequently. The test causa should be capable to test features in line with how customers use them. Keep the customers ’ requirements up front when writing good test cases. This is especially true for running usability tests and handiness tests.

• Understand user personas

A outstanding way to understand user requirements is to create user personas. A user persona is basically a fictional profile of an end-user of a certain website or application. Consider the following user persona: Mike is a frequent shopper on an e-commerce situation. He is almost potential to care about a outstanding presentation that showcases the products well, map that let him add products to bag and view pricing easily. He won ’ t care about back-end mapping like API communication and so on.

Therefore, test cases must be build in alignment with this persona. Focus test cases on see the user interface so that it is easily navigable and visually appealing. Since e-commerce involves online financial transactions, protection will be of care as well.

• Aim For 100 % Test Coverage

The whole point of pen good tryout causa is render test reportage as widely as potential. Each test case must aim to cover as many features, user scenarios and as much of the workflow as possible. Plan test cases to cover each component, feature, and function outline in the SRS (software demand specification) papers.

• Use a good Test Case Management Tool

Test case management instrument are necessary for care a stable liberation cycle. They help to proffer foil so that everyone knows who is working on what. They can tag deadline, and much more. Creating good test event include expend these tools actively and efficiently. Ensure, at the beginning of a test cycle, that the management instrument is one that all QAs on a squad are proficient or at least, comfortable with.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

• Keep an eye out for dependent test cases

It is possible that a tester may find a bug, but may not be capable to replicate it. This can happen if a test case is dependent on other test lawsuit. For example, test suit X may only be executed after tryout suit Y and Z have been executed in sequence. It is best to avoid this as far as potential since bug replication or yet review of test cases incline to lead more time and attempt.

• Use mechanisation in your favor

Software prove is a rigorous and never-ending procedure. Never-ending changes and updates in features mean that hold to be run repeatedly to see that no change to the codification breaks the original, functional codebase. Doing so manually is deplete and redundant at this point.

Using like is the best way to execute such tests involving repetitive actions. results in increased productivity and bandwidth for the software tester, who can focus on writing effective test cases instead of going through the same movement each day.

Start Automating for Free

Now that we are clear with the characteristics of a good examination case, let ’ s have a look at somethings that poorly manufacture test suit have in common, so testers know what to avoid:

• They run entirely one exceptional test condition

Each test case must be built while considering multiple exploiter scenario that the site or application is expected to deal. This means testing the software faculty with all possible combination of the main conditions. Now, comprehensive testing of these combination requires presenting them in a way that early QAs can too survey them.

• They entirely cover one small-scale component of a functionality

It is ineffective to progress trial example that pore on a specific function. Instead, they need to control usage patterns and workflow. Each test case should be craft to test as much of the workflow as possible, and doing so while run across technical boundaries of the package being tested.

• They test only a specific user role

Test cases created to test a specific user persona are limited in scope and thus, less effective. The most effective exam cases verify a user ’ s journey through an coating. For instance, any business application is better examined with test cases that are mean to test total business processes. They should ideally cover a number of user roles and systems that function to initiate and complete the business process.

• They simply repeat the requirements papers

Often, quizzer will just reduplicate the demand document in their exam cases. What test cases need to do is to test “ corner-cases ”. Writing test causa for corner causa is challenging, but most rewarding because they detect the defect that are near likely to interrupt the exploiter experience.

• They are not catalogue consistently

It is possible to indite a hundred test cause rather effortlessly and pile them into a shared folder scheme. However, without systematic tagging and cataloging, it becomes a incubus when it comes to identifying a particular test case at a ulterior engagement. Test cases should be filed in a way that enables a test direction system to approach the right one at any time.

Before publish a test causa, go through the point discussed in this article. Spare yourself the fuss of get common misunderstanding so that the software in interrogation may be tested faster. Identify bugs quicker so that they may be copy and settle as betimes as possible. Knowing the characteristic of a full test case is polar for any QA or QA team if they are to successfully work for the advance of package quality and user experience.

Related Guides