The company's new Alibaba P6 was dismissed because the writing of test cases was not standardized, so it was sad to lie flat?

Preface

Test case writing is the basic skill of software testing ; There are also many people who think that test cases are the core of software testing ; The most important thing in software testing is to design and generate effective test cases ; Test cases are the guidance of testing work , It's the rule of software testing .

We will not discuss the above views here , But to sum up , You can see that , The soft skill of writing test cases is very important and necessary for testers , I believe many people don't question .

Content

It's a pity , Our company recently hired Ali at a high price P6, The probation period has not expired , He was dismissed before the Dragon Boat Festival .

Ali P6 Generally, they are required to take charge of their own affairs , I don't know the use of writing test cases , But just like a tool man , Before each test , Copy the test case according to the requirements document , It seems like a passing scene .

After development and test , Just follow the test cases , The use case may be completed in one day , The development code is well written , After the test case is executed, it is not detected bug, Then call it ： The test is over , Meet the online standard .

After the test , Test cases are worthless , It's like throwing rubbish away , Save anywhere , At last there was no trace .

In their eyes , Engage in testing , It's no different from going to Dongguan to work in the factory .

Anyway, the test cases have been written for a long time , Can become a skilled worker loved by everyone , Think about it 35 year , Glorious lay off , Go back to your hometown and enjoy prosperity .

After the last launch ,bug A lot of , Instead, I blame writing test cases for wasting time , And useless .

In this way, people who indulge in lying flat gradually find that they can't keep up with the rapid changes of technology , In the Internet industry , Don't improve yourself in time , It's easy to get caught. “ Output to society ”

In fact, the testing industry also follows a certain Moore's law , A former skilled “ Spot work ” Just grab one at the front line 8.9K The ease with which , But now I find it more and more difficult to find a job , Education is not very good , Don't say offer 了 , There are fewer interview opportunities . put down “ Lie flat ” Well , To learn , To improve yourself ！

Lu Xun once said “ You find time to study for half an hour every day , You will surpass your industry 70% People who ”

A lot of people say , I also know this truth , But where am I going to learn ？ Where do you start to learn ？

Learning with questions is the most efficient way to learn .

Catalog

One . What is a test case

Two . Why write test cases

3、 ... and . How to write test cases

therefore , Before introducing how to write test cases , First look at a software system login function test （ As shown in the screenshot below ）：

To do a test case for this login page , Where would you think about testing ？

How many test cases can a seemingly simple page function design to complete a more comprehensive test ？10 Within ？20 strip ？.......

So before giving the answer , Let's familiarize ourselves with test cases ？ What does a test case do ？ Then we will discuss how to write test cases in combination with the above cases ？

Here is a screenshot of the contents of this article ：

One 、 What is a test case

The test case ： For a specific purpose （ Prove that there is something wrong with the software ） And the design of a set of test inputs 、 conditions for execution 、 Documentation of expected results

1、 Test cases are simply documents that guide how to do tests , This document mainly records the need to verify whether the tested software meets the requirements

2、 There are two common forms of test cases , It can be shown as a template

1） One is through Excel Direct writing

—— Most projects need to be designed and written in this way

2） One is through xmind Sort out the test points directly

—— Pressed for time , When the project is not mandatory , It can be written in the form of test points —— For business process class testing , It can also be sorted into test points for testing

3、 Design and implementation staff ： Test Engineer

4、 Templates for use cases ： Describe the core of writing use cases , Most projects have their own templates for designing use cases , Common test case templates can be referred to as follows ：

In order to support new friends , Here I also share hundreds of learning materials and explanation videos carefully sorted out by me for many years , Beginners can definitely use , It's all under it , I don't say much nonsense , If you need to join my learning group, click Portal Free collection ！

Two . Why write test cases

Why write test cases , In fact, there is a problem with the product , The first person in charge first thought about why the test didn't test ？

There's something wrong with the product , Why didn't you measure it ？

Of course , Except to avoid “ Toss and back ”, In fact, the more important role of writing test cases is as follows ：

• Technology transforms requirements into specific verifiable indicators

• Document possible problems with the software

• Prevent omissions from the activities of the test process , Improve work efficiency

• Demonstration of test workload

3、 ... and . How to write test cases

Since it's so important to write test cases , So how to better write test cases ？ I think we need to meet the following points ： - Regular thinking , Put yourself in the user's shoes （ such as ： Is that how actual users use it , Will there be any abnormal situation ？） - The support of testing theory and method （ such as ： When designing test cases according to requirements , What common test case design methods can be used ？） - Product familiarity and experience accumulation （ such as ： I have already had experience in type projects , There was a problem in some way , How was it handled at that time ？） The above design use case process , There's a premise , It's patience and perseverance for testing , Plus daily conscious thinking training , To write a comprehensive use case .

1、 Regular thinking

Back to the opening question , For a basic login page , According to the conventional thinking, can you think of the test points in the following screenshots ？ actual , These test points are all from the perspective of users , The process of detailed design combined with requirements . Are there only these test points in the actual test ？

 

2、 Learn to accumulate

I believe most test engineers can think of the above basic test points , However, in the actual work of the project is different , There are also different requirements for the granularity of test cases , If for the above login module , Let's go deeper ？ At this time, you need to be familiar with the product and test experience , And the design of these points is to keep learning 、 Familiar with the project 、 Test the accumulation of .

 

3、 Theoretical support

With conventional thinking , With the accumulation of experience , It also needs theoretical support . After all, test cases are designed by people , There are inevitable omissions in this process . How to avoid ？ In fact, it needs the support of testing theory , In my opinion, there are no more than the following two aspects to think deeply about the design of use cases ：

1） Design method of test case

A key part of testing theory is to divide requirements into specific testing points , And then according to the use case design method for specific design , The key to splitting requirements is to be familiar with requirements , Add the existing description in the document , According to user scenarios 、 The accumulation of personal testing experience （ If any ）、 Split a large section of content into test points that can be designed directly with use cases , In this way, it can be directly transformed into Excel Test cases for , In this process, popular understanding is the process of splitting and refining , Until you can directly write use cases to verify a specific function point .

Among them, the well-known design use case methods are ：

- Observation

- Equivalence class 、 The boundary value

- Decision table 、 Cause and effect diagram

- flow chart 、 Scene method

- Wrong inference, etc

2） The idea of test design develops

If the existing description information has been split according to the requirements , Is it possible to ensure that there is no problem with the test ？ It's not , On the basis of the above, if we need to expand the comprehensive test , Also need to use the characteristics of the software quality model , From these characteristics , Give test case designers more thinking space . This design is more comprehensive and reliable .

Description of common software quality model features ：

- Functionality ： Does the function have , Good use

- Performance efficiency ： The resource consumption and response time of the corresponding system

- Ease of use ： Easy to understand 、 Study 、 Use

- Compatibility ： Compatible with different hardware and software platforms

- reliability ： It's not easy to have problems , If something goes wrong, it's easy to recover

- Security ： For the security of users （ The external safety of life 、 Internal information security, etc ）

- Portability ： Whether it can run trouble free under different environmental conditions

- Maintainability ： For the later repair and maintenance is convenient

therefore , For the above login function , According to the idea of the above quality model , We get the following test points ：

Four 、 At the end

Now you look back , Do you still think that logging in to this function will design dozens or even dozens of test cases ？ Obviously it's not that simple , Need to be familiar with the requirements , Split and refine , Think in a conventional way 、 The accumulation of experience 、 Theoretical support combined with the use of , Finally, it can be transformed into the results to be verified .

The first step in getting familiar with requirements , On this basis, split and refine the test points , If this process is more complex for function points , It needs the help of test case design method , For page level test points, equivalence classes are the most widely used 、 The boundary value .

Just familiar with the need , It also needs to be combined with the accumulation of experience , Starting from the characteristics of the quality model , Think about the design of function point comprehensively , Is there any missing , Whether there are special requirements for the project .

The design of use cases is not easy , Good use cases also need constant practice , Repeated revision reviews , To write great use cases .

 

Finally, thank everyone who reads my article carefully , Watching the rise and attention of fans all the way , Reciprocity is always necessary , Although it's not very valuable , If you can use it, you can take it ：

These materials , about 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied tens of thousands of test engineers through the most difficult journey , I hope it can help you ！ Including basic knowledge 、Linux necessary 、Shell、 The principles of the Internet 、Mysql database 、 Special topic of bag capturing tools 、 Interface testing tool 、 Test advanced -Python Programming 、Web automated testing 、APP automated testing 、 Interface automation testing 、 Testing advanced continuous integration 、 Test architecture development test framework 、 Performance testing 、 Safety test, etc. . Friends in need click Portal Free collection ！！！

  If it helps you a little , Everyone 「 give the thumbs-up 」 Is the biggest driving force of Xiaobian's creation , See you in the next article