How to do function test well? Are you sure you don't want to know?

No matter when you start testing this industry , The first thing you hear about should be functional testing . Through some testing methods to verify whether the developed code meets the requirements of the product ？ Of course, you also have your own understanding of functional testing , But sensory function tests seem to be less popular in the last two years , At the same time, many students really didn't do well in the function test , Just try automated testing , Test development or something , The result is that the more you learn, the more confused you become , Why is that ？ The reason is , You haven't learned the function test well yet ！

What we usually think of as functional testing is based on requirements , Take the following test process ： Demand analysis , Use case writing , Use case review , Test and verification ,Bug Regression test , Online and online regression, etc . So day after day , Year after year , Responded to a lot of needs , But I can't get recognition when I want to change my job , Let's see if this is the case ？ Now I'll take a function tester how to work , Let's introduce the knowledge that should be used in functional testing and relevant improvement suggestions .

One 、 Demand analysis , Take the initiative

Normal demand is at the time of output , The product is to analyze the value of this demand , The scope of influence and the cost of implementation . But now a lot of things are , When the demand comes, organize the review , Then develop, test and go online . Product led development model is very common , As a test, we can't lead the requirements and projects . During the requirements review , As a tester, you must understand the content of this requirement , What existing functions are affected , The operating system or category involved , And then accurately assess the workload , To prevent late testing from being insufficient due to insufficient evaluation .

also , Focus on development and product discussions , If development says which part is more difficult to implement , Finally, how to realize ？ Among them, the changes and difficulties are the parts that must be focused on when testing . You can't stop paying attention just because it has nothing to do with you for the time being , Later will bring trouble .

Third , After the requirements review , Ask the product to update all changes during this review , At the same time, a plan is given to ensure that any changes to the product are updated in time . Fourth , According to product requirements , Design test plan and schedule , At this point, we can consider coarse-grained , Time should be reasonable ; At the same time, discuss with the participants .

Two 、 Use case design and review , Do not leave anything missing

Test case is the work that every tester must complete in the process of working , Whether you use it or not Excel, Or use it FreeMind To write , In the test work, one is used to guide the test work , And it is a document of related business . Maybe you don't care much about writing test cases , But in my previous interview experience , More than half of the people write test cases that are not up to standard . Many people write use cases in the way of books , What boundary value method , Conditional covering method, etc , In fact, we should pay more attention to users , It's right to write use cases from the user's point of view .

The test case name that the test case must have , Execution steps , The expected results of these three points must be clearly written . Moreover, the selection of test scheme must be comprehensive , As a functional tester, you may not be able to write automated test scripts , No performance testing , Security testing , But you must be able to think about what kind of testing to implement according to your needs . Such as giving you a scene during the interview ： A brand new App To publish , If you're going to test , What test solutions can you come up with ？ If you can only think of how to test app The function of , As a functional tester, you just don't think comprehensively . At this time App The function of ,App Performance of , Security of data transmission , Functional testing of interfaces or services , Automated testing and monitoring of interfaces or services , Performance testing of interfaces or services , The storage and disaster recovery of underlying data must be taken into account .

When designing use cases, we should design two types , One is to develop smoke test cases with self-test and acceptance test standards , One is comprehensive test cases for requirements . After writing use cases, actively contact relevant personnel for use case review , Emphasize the development of self-test , Modify inappropriate use cases when involved in the review process .

3、 ... and 、 Testing process , Focus on project control

In fact, the process control of the project should be paid attention to at the beginning of requirements , It's just that a lot of times we don't realize that this is the job of testing , There are products to control , There are special project managers to control . Testers are front-line staff , No matter how long you work , Must have the awareness of paying attention to the overall project . If you don't focus on project progress , When do you start the test , In the process of testing, you will encounter that the content of the test is inconsistent with the original requirements , Add new content to increase the workload , Or when products and development work together to reduce test time , It's hard for you to work overtime .

Once the need is clear, it's up to you , We should always pay attention to the situation of the project according to the schedule . In the middle of changing requirements , To assess if it will affect the project schedule , If it affects rescheduling . If the development and testing are late , Whether it affects the online time , If it may affect , An early warning email will be sent to relevant personnel soon , Let us know the details . And in the process of testing , Found out bug The problem must be described in detail , Whether it's jira, Zen or something bug Management style , One bug Write down the following points ：Bug Problem description ,bug Repeat step , Whether there are preconditions , Expected results , The actual result , To facilitate development to modify . At the same time bug Accurate classification , Tracking progress in real time , Ensure that the project is completed on schedule .

Four 、 Online regression and project summary

After a requirement is online , Online return in time , If necessary, relevant personnel must be reminded to carry out automatic online regression or monitoring . At the same time, we must return to the original functions that may be affected when we review the requirements , To ensure that the new features are fully launched successfully . As a functional tester , After a project is completed , Whether or not the company requires , Make a corresponding text summary of the project . Summarize the problems encountered during the whole project , The final solution or the solution discussed at that time , What should we pay attention to ？ What can we learn from the program or improvement strategy ？ Is there any problem of generality in the project .

If the company has corresponding project summary plan , When testing, you should pay more attention to some data , If the smoke test is passed at one time ,Bug Number and different levels of bug Count , Participate in the corresponding of developers Bug Count , Mention the number of tests , Online times, etc . Then use the third-party tools to chart the corresponding data , Then summarize the relevant problems , All improvement plans need to be summarized in detail .

5、 ... and 、 Summary and precipitation of ability

When we were looking for a job , Many students who have been doing functional tests for many years generally find it difficult to pass the interview , What is the reason behind this ？ In fact, the core reason is , You don't have the ability to work for the corresponding years .

Use of test tools ： In your past work experience , Have you summarized what kind of requirements or what kind of testing tools should be used in the project , Instead of just using tools provided or specified by the company ？ Have you analyzed the advantages and disadvantages of similar tools ？ If a similar brand-new product , Can you focus on the needs of your work , Prepare appropriate testing tools to assist in testing ？ What kind of testing tools may have problems when testing the project , What is the solution to the problem ？

A summary of the problem ： Summarize the problems in the deployment environment in the test work 502 or 404 Causes and solutions ？ Which function of the product is prone to problems , Or there may be problems in developing how to realize the corresponding functions ？ How the functional modules of the product work , Modification of some functions may affect other modules ？ Which version of the compiler packages products that are prone to problems ？ Wait, has the corresponding problem summary been done , If done , After receiving the corresponding requirements, we can quickly evaluate the test scope , Select test plan , Planning test time, etc .

The precipitation of Technology ： Technology doesn't just mean coding ability , As usual, when we have problems with our deployment environment , A summary of the final solution ; Troubleshooting of null pointer in log during test ; Problems and solutions encountered in project testing ; Troubleshooting and solutions to some common problems, etc . Be good at accumulating in your work , So as to guide their work or provide colleagues with ideas and methods to solve problems .

Always ask yourself a question ： Leave the existing platform , What else do I have ？ This is your capital , Familiarity with the company's business , The company is now using tools and so on , There is no advantage for you . And the mastery of similar business processes , Overall control of the project , Quickly understand the business and be able to choose the test plan according to the needs , Introduce existing testing tools to improve testing efficiency , The ability to predict and solve problems in the process of testing is what the function tester must have . Have you done that ？ Business experts are also a good choice for testers who don't want to be coding , Don't complain about functional testing all day , We should fully understand the current situation of the industry and our own advantages and disadvantages , Make a career plan .

A little help

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 !

The house needs to be built layer by layer , Knowledge needs to be learned at one point one . We should lay a good foundation in the process of learning , More hands-on practice , Don't talk much , The last dry goods here ！ I stayed up late to sort out the stages ( function 、 Interface 、 automation 、 performance 、 Test open ) Skills learning materials + Practical explanation , Very suitable for studying in private , It's much more efficient than self-study , Share with you .

Get off w/x/g/z/h： Software testing tips dao

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .