Share the basic knowledge of software testing and write something you don't know

Catalog

One 、 The test case

Two 、 unit testing

1、 Purpose

2、 Main task

3、 The steps of unit testing

3、 ... and 、 A functional test

1、 A functional test

2、 Compatibility test

3、 Security testing

4、 Input box test

5、 User rights test

---

One 、 The test case

1、 What is a test case

A set of preconditions 、 Input 、 conditions for execution 、 Expected results, etc , Data to complete the test of a specific requirement or goal , Reflect the test plan 、 Method 、 Technical and policy documentation

2、 Why write test cases

Organize and plan the test steps scientifically and effectively , Easy to manage , Record

3、 What are the main test cases Content

Number 、 date 、 Design and testing personnel 、 priority 、 title 、 The goal is 、 Environmental Science 、 input data / action 、 Expected results

4、 What is required to write test cases

Software requirements design specification 、 Software template

5、 Considerations for designing test cases

From high to low , independence , One to one correspondence with functions , Design on demand , Designed by experienced personnel

6、 Principles for designing test cases

There are templates , correctness , Representative , Justiciability , Reproducibility , Detailed, accurate and clear steps , Conform to specifications

7、 Use case management tools

There are many use case defect management tools on the market ： Stung a few ：mantis、redmine、jira、bugzilla、 Zen way, etc

8、 Use case management process

To write → review （ modify → Review again ）→ Use → Preservation management → maintain / upgrade

9、 Test case content

Description of the goal 、 Environmental Science 、 Input and output data / action 、 step 、 Expected results 、 Remarks, etc

                               

 

Two 、 unit testing

An act of verification , Every item in the program needs to be verified

1、 Purpose

①、 Check the internal error of the unit module , Provide basis for software review

②、 Test important paths within the module , Based on program design specification and test data , To check for errors

③、 Check whether the information flows into and out of the unit correctly

④、 Integrity of internal data 、 The correctness of the relationship between data forms , And the processing and influence of global variables in the cell

⑤、 Whether the data works normally at the boundary

⑥、 Whether the operation of the unit can meet the logical coverage of the characteristics

⑦、 Whether the error handling mechanism is effective

2、 Main task

Program syntax check 、 Program logic check 、 Module interface test 、 Local data structure test 、 Path test 、 Boundary condition test 、 Error handling tests 、 Code writing specification check

2.1 Program syntax check

①. Compile the language to check the program

②. Manual inspection

2.2 Program logic check

①. Check whether the program logic is correct

②. Whether there is a problem with the upper and lower items of the loop statement and the number of loops in the program

③. Whether the function or sub module has self calling problem

2.3 Module interface test

The module interface is the key part of the module kernel ; When a module is called externally , The data must flow correctly , When the module finishes processing the problem and returns to the calling module , Data must flow out correctly

2.4 Local data structure test

The local data structure is to ensure the data temporarily stored in the module , The root cause of module errors is often local data structures

The form of expression is as follows ：

①. The most common accumulation errors in local data structure testing

②. Description of unsuitable or incompatible types

③. Variable has no initial value

④. Error in variable initialization or default value

⑤. Incorrect variable name or incorrect truncation

⑥. Overflow 、 Underflow or address exception

2.5 Path test

Test the important execution paths in the module , Path errors are mainly caused by incorrect calculations , Incorrect comparison or abnormal control flow leads to

2.6 Boundary condition test

Error prone factors ：

①. There is a... In the program n Secondary cycle , This n The second cycle should be 1~n, instead of 0~n

②. By less than 、 Less than or equal to 、 be equal to 、 Greater than 、 Greater than or equal to 、 Not equal to the determined comparison value. Error

③. Overflow 、 Underflow and address exceptions

2.7 Error handling tests

Perfect module design requires that error conditions can be foreseen , And set appropriate error handling , So that if the program goes wrong , Can rearrange the wrong program , Ensure its logical correctness

2.8 Code writing specification check

①. Flow chart of module design program framework

②. Code writing specification , Alignment mode

③. Comments to code

④. Parameter type , Data length , The pointer , The length of the array    size

⑤. Input and output parameters and results

3、 The steps of unit testing

Unit testing is the single debugging for each program , The main steps are divided into program syntax check and program logic check

                     

 

3、 ... and 、 A functional test

Definition ： Function test is to verify the functions of products , According to the functional test cases , Test one by one , Check whether the product meets the function required by the user ; You only need to consider its function points, not the internal structure and code of the software

WEB：

1、 A functional test

1.1 Link test

  Links are web A very important feature of an application system , It is mainly used to switch and jump between pages , The main means to guide users to some pages that don't know the address , Link testing generally focuses on three points ：

①. Does the link follow the established instructions , It is indeed linked to the interface of the link

②. Test whether the page linked by the link really exists

③. Ensure that there are no separate pages in the system （ That is, there is no link to , Only through the correct URL Address to access ）

1.2 Form test

It can also be understood as data landing ; When the user web When submitting information to the server on the application system , You need to use form operations , such as , User registration , Sign in , Information change, etc ; In this case , We must test the integrity of the submitted information , To verify the correctness of the data submitted to the server ,

Of course , This also involves some normal logic , such as , Date of birth and occupation , Whether the working years are appropriate , The matching between local provinces and urban areas , If the setting uses the default value , It also needs to be tested .

1.3 Navigation test

As a test , Many times we have to think from the perspective of users , Most users are goal driven , When he visits a website or web System time , Will quickly browse the system , When you can't find the information that meets your needs , Will leave soon , Few users are willing to take the time to familiarize themselves with the structure of the system ;

Navigation test , That is, between different page jumps , Or button , Dialog box , Lists, windows, etc , By considering these factors , To determine whether an application system is easy to navigate ： Is it intuitive ？ Whether the main modules of the system can be accessed or reached through the home page ？

Whether the site needs in-house map or search engine and other help ？web Another key point of system navigation is page structure 、 Navigation 、 menu 、 Whether the style is consistent , Make sure that users can find what they want by intuition or simple judgment .

1.4 Graphic test

It can be understood as UI test , It includes pictures 、 Animation 、 Frame 、 Color 、 typeface 、 background 、 Buttons, etc .

The following key points should be considered ：

①. Pictures should have a clear purpose , representative ; Try to keep the picture size as small as possible , It is generally used JPG perhaps GIF Compress

②. Whether the overall style of the page is consistent with the purpose of the system

③. The background color , typeface , Whether the collocation is reasonable

1.5 Content testing

Mainly used to detect web Accuracy of information provided by the system 、 The correlation , such as ： prices for goods , A word description ; Accuracy of information , Are there any spelling mistakes ; Relevance of information , For example, many websites “ List of related articles , Video list, etc ”

1.6 Overall interface test

That is what we often call the user experience . Whether the user feels comfortable when browsing , The overall style is generally in the form of a questionnaire , To determine the feedback from users , It is better to have the participation of the end users

2、 Compatibility test

2.1 Platform compatible

There are many operating systems , such as Windows、Unix、Linux、macintosh etc. ; Which system the user uses depends on the user , therefore , System compatibility testing is necessary .

2.2 Browser compatibility

Browser is web The core component of the client , Different browsers , Yes Java,JavaScript,css perhaps HTML The specifications of all have different supports ; in addition , The adopted frame and structure style can be displayed or not displayed in different browsers , Different browsers have different security settings .

Test browser compatibility , One way is to create a compatibility matrix , To test the compatibility of different versions of browsers from different manufacturers .

Such as test IE browser , It can be done through a program called IEtester To test compatibility , Or through F12 Console to switch the browser version to test the compatibility with the display of some previous front-end elements

3、 Security testing

The main areas of security testing are as follows ：

3.1 Validity of user name and password , Pay attention to case sensitivity , Time limit , Whether you can browse some pages without logging in

3.2 Whether there is a timeout limit

3.3 Test whether the relevant information is written to the log file during user operation 、 Traceable, etc

3.4 If a condom is used , You need to test whether the encryption is correct , Information integrity before and after encryption , correctness

3.5 Without authorization , Whether the script can be placed and edited on the server or front-end

4、 Input box test

Here are some notes ：

4.1 Verify the consistency of input and output information

4.2 Whether the text prompt in front of the input box is correct

4.3 Processing of special characters 、 distinguish ： Single and double quotation marks , Brackets , comma 、 Semicolon, etc , And case status , Half width and full width

4.4 The size of the input box 、 length 、 Borders, etc

4.5 Input of different characters , And the processing of character combination （ Numbers + Letter + Character etc. ）

4.6 On Spaces 、tab Processing mechanism of newline key

4.7 Password input box character asterisk or other asterisk line conversion , encryption

4.8 Whether there is a limit on the length of input characters in the input box

4.9 The color of the character itself , Specifications, etc

4.10 Some input fields need to be restricted , In case of wrong input , Is there a hint ？ Whether the prompt is simple and reasonable ？

4.11 Input status , In some cases, the input box is not editable , When it is in the editing state again , Whether the input state of the input box has changed

4.12 Input type ： Allow copying, pasting, cutting and other input operations

4.13 Whether the keyword supports wildcards , And keyword search ability , Sensitive words, etc

4.14 The case where a space is entered in the input box

4.15 For example, login and register , Determination of input conditions ： Whether to input , Whether the input is correct, etc

5、 User rights test

User permissions , That is, what rights the account has to perform operations

5.1 After giving permission to an account , Log in to this account , Check to see if you have the given permission , And whether the permission settings are correct （ Whether the permission exceeds or is insufficient ）

5.2 Delete or modify the account permissions that have been logged in and are performing operations , Whether the program can correctly handle , verification

5.3 Re register the system and change the login identity before logging in , Whether the program can be executed correctly , Can I continue to use my previous permission

5.4 In the case of work assignment or role management , Delete the workgroup or role containing the user , Whether the program can correctly handle

5.5 Log in to the same system with different permissions , Whether the permission scope is correct

5.6 Can I leave the information blank 、 Add permissions to the account with a long user name

5.7 Whether to delete the system administrator or modify the administrator permissions ？ The actual situation after deletion or modification

5.8 Can logged in users modify or delete their own or others' permissions , Information

5.9 Add users （ Having a number or identification ）, The combination of different user names and identities , Whether permissions can be handled correctly

5.10 After modifying user permissions or information , Does it affect other modules

5.11 If the modified user information is the same as other existing user information , Whether the modification is successful ？ Whether there is corresponding prompt

5.12 Modify some settings , Whether the permission of the account is the same as or higher than / The permissions of other accounts lower than this account are affected

5.13 Whether the same user can belong to other groups at the same time , Whether the permissions of each group can be crossed

Thank everyone who reads my article carefully ！！！

If you can use the following information, you can take it away directly ：

1、 Self study development or test the necessary complete project source code and environment

2、 Test all templates in the work （ test plan 、 The test case 、 Test report, etc ）

3、 Classic interview questions for software testing

4、Python/Java Automation test practice .pdf

5、Jmeter/postman Interface test full set of video acquisition

I personally sorted out some technical materials I have sorted out in my software testing career in recent years , contain ： e-book , Resume module , Various work templates , Interview treasure , Self study projects, etc . You can call me if you need .