My experience in functional testing for so many years

Catalog

1、 Preface

Two 、 Skills required for functional testing

2.1  Skillfully use SQL

2.2 Linux

2.3 Using a database , Follow the data flow

2.4 Write test cases

2.5 http And https agreement

2.6 Know the business

2.7 bug management

2.8 A typical bug

3、 ... and 、 Summary

---

1、 Preface

Functional testing is the basic skill of test engineers , Many people don't do well in functional testing , Just want to do performance testing 、 automated testing . Many people have little understanding of functional testing , How to understand without your heart , To study the , Then your career will stop at a little bit . ad locum , I write down my understanding of functional testing .

Two 、 Skills required for functional testing

2.1  Skillfully use SQL

1、 frequently-used sql Statements must be written . For example, add, delete, modify and check .

2、 Understand database transactions 、 Write stored procedures 、 Familiar with common system functions .

3、 Understand and be able to backup the database 、 transfer 、 Restore 、 Mirror and so on

4、 Yes sql Statement to tune , And you can monitor the running statements to see their performance

5、 Understand database cluster and other operations .

2.2 Linux

Linux It is the basic skill of testers , You don't need to master something that's too difficult or unusual Linux command , You can check the log normally , The positioning problem is OK .

1、 Basic commands

frequently-used Linux Basic commands , Interview often ask , Or give a scenario , Ask what command you use .

Specific please see ：https://www.cnblogs.com/bianfengjie/p/9213180.html

2、 Check the log

Junior testers often encounter , Find out bug, Situations that developers do not recognize or are unwilling to solve , How can testers get rid of this problem ？

That's what we found bug According to the log level , To check the log , Location problem .

First of all, let's talk about the log level .

First of all, remember this ： The higher the log level , The less information you output .

The specific log levels are divided into four levels ：

                                    info : Code info Information , barring sql Sentences and so on debug Information
                                    warning warning : Code warning message
                                    error : The program itself reports an error message java.lang.outindexERROR.....
                                    critical ： Hardly use

Generally, it doesn't meet the demand bug stay debug in , The program itself reports an error bug stay error in .

                            

 

2.3 Using a database , Follow the data flow

About databases , See another blog post .

1、 The essence of database

Common databases are MAYSQL、ORECAL、Redis

among Mysql Database is a typical relational database

2、 Database operation

  （1） Database and table operations

  （2） Table data operation

  （3） complex sql Inquire about

2.4 Write test cases

A very important type of document in the testing process , It is the core of testing work 、 Is a set of input and output standards when testing 、 It's a specific comparison of software requirements . Write test cases , It's the basic skill of the tester , But not many people can really write well .

What test cases must contain ：

Use case number 、 Use case name 、 Test background 、 precondition 、 priority 、 Importance level 、 Test data 、 testing procedure 、 Expected results 、 The actual result 、 remarks .

1、 Test case writing process

Demand analysis -> Extract test points -> Test case writing -> Test case review

2、 The idea of writing test cases

（1） According to the product RPD, Extract test points .

（2） According to the direction of data flow .

（3） Deploy according to your architecture .

（4） Common methods of writing test cases ： Division of equivalence class 、 Boundary value analysis 、 Flow chart method, etc .

（5） Coverage weak network test 、 The interface test 、 Security testing 、 Performance test, etc .

（6） Common test tools are ：Postman、 Charles、 Fiddler 、Jemter、Loadrunner etc. .

3、 Considerations for writing test cases

（1） Design test case table according to the actual situation of the project

（2） Don't copy the use case format mechanically

（3） Prepare according to the specific situation

（4） Learn to question needs , Don't write test cases exactly according to requirements , Understand requirements from the perspective of customers and products , See functions and experiences beyond the needs

4、 Manage test cases

Why manage test cases ？

（1） The number of test cases is huge

（2） The test case will change according to the requirements

（3） Test cases need to be supplemented and improved for a long time

How to manage test cases ？

（1） The original Excel management

（2） Professional project management system （eg：git、 ZenTao 、JIRA、Confiuence etc. ） Typically for web Format

Specific reference ：https://blog.csdn.net/sdr_zd/article/details/70453027?locationNum=6&fps=1

2.5 http And https agreement

Relationship with HTTP and HTTPS agreement , Please click on ：https://www.cnblogs.com/bianfengjie/p/9213131.html

Interviews are often about Http The following issues of the agreement

1、Http Protocol principle

2、http and http The difference between agreements

3、TCP and UDP The difference between

4、session and token The difference between

5、 Understanding of public and private keys

6、get and post The difference between

7、 From input URL What happened to the page load

8、 What is an agent , Forward and reverse proxies ？

                   

 

2.6 Know the business

Do a function test , Be sure to understand the business , Even understand the business . Only by thoroughly understanding the business , Only in this way can the function test be done well , And there is a certain improvement .

After getting familiar with the business , Will know a lot of common sense , After knowing the following common sense , You can try advanced , Learn to do automated tests 、 The interface test 、 Performance testing

 1、 When to intervene in Automation => When your system becomes stable
 2、 When to intervene in interface testing   => When the interface is developed
 3、 When to intervene in performance testing => When there's a promotion , Or rush to buy (618 Great promotion , Grab train tickets for the new year , Grab coupons )
      for instance ,5000 Zhang coupons , About how many people robbed , How long will it take to finish

2.7 bug management

Do a function test , Another important job is bug management , An excellent Tester , on-line bug A lot , More than other colleagues you work with , But online bug Very few , Less than other colleagues .

1、 bug Definition

（1） Not meeting the requirements  
（2） The program itself reports an error  
（3） Not in line with the user's usage habits

2、bug Life cycle when we testers submit a bug When , From the beginning bug There is its life cycle , From the beginning to

end , The life cycle is as follows

3、bug Single content

Bug describe （summary）
environmental information ： operating system / database / browser / Software version (OS/Database/Project/Build/Release)
The function module belongs to
test / Developer
Severity level (1-5)
Customer priority
The degree of risk
state
Repeat step
The actual result
Whether to return to the question
etc.

Specific reference ：https://blog.csdn.net/ewq159/article/details/79500546

4、 Test report

Document the test process and results , Analyze the problems and defects found , To correct the existence of software Provide basis for quality problems ,

At the same time, it lays the foundation for software acceptance and delivery. The test report is the same as the test plan , commonly By testing leader To write , Testers need to know What are the contents of the test report

2.8 A typical bug

     1、 Bag grabbing effect : Test one app Search function , Grab the bag , Catch a search interface , I suddenly found that I caught two request interfaces -> When the traffic comes up , The pressure of service has tripled
     2、 Trend of data flow : During the test, I found that there was only one piece of data on the page , But there is one more in the database -> 1、 Data volume increases , Queries slow down 2、 Too much dirty data , Instant full , The program crashed

     3、 Weak network test ：app The project must have Weak network test （ simulation 2g、3g、4g,wifi Network status and packet loss ）; Network switching test （ Disconnect the network and reconnect 、3g Switch to 4g/wifi etc. ）

3、 ... and 、 Summary

  Sum up , It's not easy to do a good job of functional testing . I did two years of Internet function test to , I still don't understand a lot of knowledge , Just keep learning , You can become a talent by yourself .

Many people can't do well in functional testing , Just want to do performance testing 、 automated testing , It's actually aiming high , I think the foundation has been laid , Then learn performance testing 、 Automated testing or something , It must get twice the result with half the effort .