Some experience functional test
I. Introduction
Functional test
is the basis for the work test engineers, many people still do not function tests, I wanted to do
performance testing
,
automated testing
. Many people understand the functional test is little point, how they do not have the heart to enlightenment, to study, then your career will stay on a little point. Here I write down my understanding of the functional test.
Second, the functional tests required to master the skills
2.1
familiar with SQL
1, commonly used sql statement will write. For example, CRUD and the like.
2, to understand
the database
transaction will write stored procedures, skilled commonly used system functions.
3, can be understood and database backup, migration, reduction, mirroring operation
4, sql statement tuning, and you can view the performance of the statement surveillance operation
5, to understand database cluster operations.
2.2
Linux
Linux is the basis for the work of testers not need to master difficult or very common Linux commands can do normal view logs, location problem on it.
1, the basic command
Commonly used Linux basic commands, often ask interview, or given a scenario and ask you what order.
2, View Log
Junior testers often encountered at work, find
bug
, developers does not recognize or unwilling to solve the case, testers how to get rid of this problem?
According bug that is found according to the log level to view the log, locate the problem.
That first thing to say here about the log level.
First, remember this: the higher the log level, the less information output.
Specific log level is divided into four levels:
info: info Information Code does not include some of the debug information such as sql statement
warning warning: a warning message Code
error: the program itself being given the information
the Java
.lang.outindexERROR .....
critical: almost less than
Generally do not meet the needs of a bug in debug, a bug in the program itself being given in error.
2.3 database, with data flow
On the database, see another blog post (MySQL).
1, the nature of the database
The main common database is MYSQL, ORECAL, Redis
Mysql database which is typical relational database
2, database operations
(1) database and table operations
(2) Operation table data
(3) complex sql query
2.4
write test cases
Very important in the course of a test class documentation, which is the core testing, is a set of inputs and outputs in the testing standards, specific control software needs. Writing test cases, testers are basic, but really, not many people can write.
Test case must contain the contents:
Example No. use, use-case name ,, testing purposes, priority, important level, pre-conditions, test procedures, expected results, actual results, notes. (Different templates of different companies, basically almost)
1, the preparation process of test cases
Requirements Analysis -> extraction test points -> write test cases -> Test Case Review
2, the idea of writing test cases
(1) according to RPD product extracted test point.
(2) to the data stream.
(3) According to the deployment architecture.
(4)
common method to write tests: 8 Equivalence partitioning method method, boundary value analysis, determination table method, the causal diagram, scene method, the test method Kang, orthogonal arrangement method, the error inference methods ( focus).
(5)
covers weak network testing
,
interface testing
,
security testing
,
performance testing
and the like.
(6)
common testing tools
: Postman, Charles, Fiddler, Jemter , Loadrunner and so on.
3, write test cases Notes
(1) test cases form the actual situation of the project
(2) a format not mechanically Example
(3) the preparation according to the specific circumstances
Questioned the demand (4) to learn, not to write test cases in full accordance with the needs, from the perspective of the customer and the product needs to understand, see and experience beyond the demand function
4, test case management
Why do you want to manage test cases?
A huge number (1) test
(2) test cases will change according to changes in demand
(3) test cases need long-term supplement to improve
How to manage test cases?
(1) The original Excel Management
(2) Professional
project management
system (eg: git, Zen,
JIRA
, Confiuence, etc.) generally for
web
format
2.5 http and https protocol
The following interview is often Http agreement on several issues
1, Http principle agreement
2 difference, http and https protocols
3, the difference between TCP and UDP
4, the difference between a cookie and sessiond
5, public and private keys of understanding
6 difference, get and post the
7. What happened to enter the URL from the page loads
8, what is the proxy, forward proxy and reverse proxy?
2.6 understand the business
Do functional testing, we must understand the business, or even understand the business. Only thoroughly understand their business, in order to do functional testing, and there is some improvement.
After familiar with the business, will know a lot of common sense, common sense we know that after the above, you can try advanced,
learning to do automated testing, interface testing, performance testing (focus)
1, when the intervention Automation => When you stabilize the system
2, when the intervention interface test => When completed interface development time
3, when to intervene performance test => when there is promotion, or when snapped (618 big promotion, the New Year rush tickets, grab a coupon)
For example, 5000 coupons, about how many people grab, grab finished how long
2.7 bug management
Do functional testing, there is a very important job is to manage bug, a good tester, online bug very much, more than other colleagues and you work together, but online bug is very small, less than other colleagues.
1, bug definitions
(1) does not meet the needs of
(2) the program itself being given
(3) does not meet the user's habits
2, bug life cycle when we testers to submit a bug when the bug beginning to have its life cycle, from start to
The end of the life cycle is as follows
3, bug list content
Bug description (Summary)
Environmental information: OS / database / browser / software version (OS / Database / Project / Build / Release)
Function module belongs
Testing / Developer
Severity Level (1-5)
Customer priority
The degree of risk
status
Steps to Reproduce
actual results
Do you want to return to the issue
Wait
4, the test report
The process and the results of tests written documentation of the findings and defect analysis, provide the basis for remedying the software quality problem,
At the same time lay the foundation for software acceptance testing and delivery of reports and test plans as generally written by the test leader, test personnel need to know
What about the test report has
2.8 A typical bug
1, packet capture function: a test app search, capture, caught a search interface, suddenly found caught two requests Interface -> When the traffic coming up, service of pressure rise twice
2, the data stream to: test, it was found that only the data on a page, but there more than a database -> 1, the data becomes large, slow query 2, too much dirty data, instant full, program crashes
3, the weak network testing: app test items must be weak network (analog 2g, 3g, 4g, wifi network state and packet loss); network handover test (after reconnecting disconnected from the network, 3g switch to 4g / wifi, etc.)
III Summary
To conclude, do a functional test is not an easy thing. I did two years of
the Internet
function tests, or do not understand a lot of knowledge, only the continuous learning that he can become useful.
A lot of people function tests are done, you want to do performance testing, automated testing, in fact, is ambitious, I think lay the foundation, to learn a performance testing, automated testing what, certainly more with less;
And automated testing, interface testing, performance testing functions you need while working in you to do a functional test of time while learning, learning step by step, to gain experience.