Shulou(Shulou.com)06/03 Report--

I. definition

A test case (Test Case) is a set of test inputs, execution conditions, and expected results developed for a particular goal to test a program path or verify whether a particular requirement is met.

First of all, the test needs to ensure the following two points:

The program did what it was supposed to do.

The program doesn't do what it shouldn't do.

Therefore, as the basis of test implementation, test cases must be able to fully cover the test requirements, rather than judging the quality of a single Case.

Second, how to design test cases

1. Know enough about the version under test

Interpret product requirements documents in rough and detailed steps, such as interactions, functional processes, boundaries, constraints, and so on. Fully understand the principle of technical implementation (logical principle, architecture and dependence on other platforms, interfaces, etc.). In-depth understanding of the user group, analysis of user scenarios, possible use methods and user psychology, completely from the user point of view, to design the Case, while making some judgment on the user experience.

2. Design Case priority

In general, after writing Case in BugFree or Zen tools, you can filter priorities by priority. If you use Excel documents to write, you can identify the corresponding priorities by different background colors, regardless of review or implementation, you can check here. Whether it is smoke test cases or functional test cases, save a lot of time.

3. Analyze the requirements from coarse to fine

You can use tool assistance, the first round of requirements analysis, roughly draw the test requirements framework; the second round of requirements analysis, start to extend each sub-test point; refine the test point, you can refer to or reference the written public Case, but also take into account the characteristics of this function in the tested version. Another thing to consider is to grasp the granularity of the test points.

4. Test case Update

Requirements changes may occur in both the requirements analysis phase and the development phase, so the test points roughly sorted out in the early stage need to be updated synchronously in time. In addition, during the Case review phase, there may be Case redundancy or omissions, and it also needs to be repaired in the Case pool in time after the review. If there is a requirement tool in the project, you can use the tool to synchronously notify the person in charge of each node, which will greatly reduce the time of UPdate.

Third, how to quickly improve the design Case ability of novice

1. Be very familiar with business

This is a prerequisite because all Case starts at the business layer, and the end user takes the business as the starting point.

2. Cultivate users' thinking.

Testers need to analyze what users need, what they want and what they don't want from the customer's point of view, which is helpful for us to better mine the implied requirements. Therefore, the design of the scene is also from the user's point of view.

3. Don't limit testing thinking.

For good testers, they will have their own general test case table. Every time they write a test case, they will pick out the repetitive or common functions and refer to the existing general Case. However, if it can not be updated in time, with the change of the company's project, it is likely to rest on its laurels in some projects and cannot be used flexibly. So GM Case summary update is essential, can also be shared for peer advice, brainstorming, maybe others have more novel methods, which will continue to develop their own testing thinking, rather than repeating the original experience.

4. Be willing to share and sum up in a planned way

Make a detailed plan for your learning process, quantify it to the sky, and arrange what you want to learn every day. At the same time, the most important thing is to form the habit of summarizing, summarizing every day, summarizing each project, summarizing test methods, summarizing Bug reasons, bizarre Bug, etc., which will be valuable assets for your future work. At the same time, if you take the initiative to sum up for a long time, you will find that you have a qualitative improvement, and you will be more comfortable with your current job, so experience is accumulated over time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.