How does a new tester do functional testing?Test thinking is really important

01Importance of Test Fundamentals

If you are new to testing, testing basics is very important to you.The basic knowledge I am referring to here is not simply about what is software testing and the purpose of software testing, but the ability to design test cases.

What are the testing methods for software test cases?

Answer: Equivalence classes, boundary values, causal diagrams, etc.

It is necessary to describe the more commonly used test case design methods in combination with actual business scenarios.

A: Many replies are explained by logging in.

In other words, in normal work, there are only a few more commonly used use case designs. If you can apply the theory to practical work, then it will be easy to raise your salary, in other words.

So, how do you design good test cases?

It is very important to design use cases in combination with actual business scenarios. The use cases do not involve today's functions, but also need to take into account the business associated with upstream and downstream, and cover as much detail as possible.

02Improve database processing capabilities

As a qualified tester, database additions, deletions, modifications, and related queries are necessary subjects.But for the novice testers, this difficulty seems to be a bit big, and many people tend to pay attention to appearances before doing things.

For example: click save, submit and save, can you tell that the save function is normal?

The real correct way is that you must go to the database to check the status of the data in the database, and confirm whether the field value is stored correctly. Involving business-related functions, you also need to go to the database to further confirm the accuracy of the data..It is necessary to be aware of the flow of business data.

03 Ability to locate problems

During the testing process, people often encounter interface errors and abnormal error messages.As a test rookie, your first reaction may be to throw it directly to the developer: "Hey, brother, you reported an error here."

But when the developer asks: "Is it the front end or the back end reporting an error?"

You may be left with nothing but a daze.Because most of the software is currently separated from the front and back.Therefore, what you need to do at this time is to learn to read the log.

According to the log, analyze and judge whether it is a front-end or back-end problem, including: using the packet capture software to identify whether the front-end value is transmitted incorrectly, or the back-end logic processing error and other related problems.And according to the initial positioning of the problem, help developers improve the efficiency of solving problems and so on.

04 Capable of summarizing

As new testers, we need to summarize a lot.

There was a classmate who had just graduated. He had a set of his own summary methods, such as: combing and summarizing/combing business according to XMind, recording the handling methods for problems encountered, and forming his own experience summary in the test work.He shared his own way with the team. The student grew very fast in the company and was promoted due to his outstanding performance.

As a technical student, the ability to summarize is very important. In normal work, everyone will step on various pits, summarize and summarize the problems encountered to form experiences and share them with others. In the competition, they can also be moreProminent, you can turn it over and look at it from time to time in subsequent work, and each time you have a different harvest.

05 Do a good job of ability improvement in a timely manner

The constant topic of technicians: the improvement of technical strength.

Newcomers grow up very fast in the early stage. During the test, they can think more and think about whether there is a better way to solve the problem.

I heard before that many newcomers are impetuous and always want to use automation to solve problems, but the level of automated testing is limited, and problems arise one after another.

Basically, it can be said that if you haven't learned to walk, you want to run.We can lay the foundation first, do functional testing well, and consider how to conduct testing more efficiently/highly under the understanding of the business situation.

Because, in other words, when some students are dealing with testing work, they are often automated for the sake of automation. Many automation frameworks have not been applied to the work, nor have actual value, and have not yet thought of themselves.It is suggested that you can create a framework first, then introduce certain thinking, and do automated testing in combination with the business.

For example, you can start with specialized tools that are already on the market.

For example: the interface testing tools jmeter/postman, etc., first understand the interface testing process and methods based on special tools, and then combine with their own business to find problems that cannot be solved by today's testing tools.Later, combined with the business development platform, we will continue to think and practice.

I firmly believe that through a period of training, everyone will be able to improve the test level to a certain extent.Come on, I firmly believe that tomorrow will be better!

Finally give the testers a bonus

It's just a thank you to everyone who reads my article carefully. There is always a need for a courtesy exchange, although it's not a very valuable thing. If you can use it, you can take it directly:

p>

These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse also accompanies tens of thousands of test engineers through the most difficult journey. I hope it can also help you!

strong>You can click the small card below to get it