当前位置:网站首页>Software testing -- Classification of tests

Software testing -- Classification of tests

2022-06-21 23:57:00 Pinellia tuber is cool

Catalog

By test object

Interface tests

Reliability test

Fault tolerance test  

Document the test  

  Compatibility test

Ease of use test

Standardization and standardization  

Intuitiveness  

flexibility  

comfort

Install uninstall test

Security testing  

Performance testing  

Memory leak test  

By whether or not to view code  

Black box testing

Black box test method

White box testing

Test method of white box test

Grey box testing

By development stage

unit testing

Integration testing  

The system test  

regression testing

Smoke testing

The acceptance test

Divided by test implementation organization  

α test

β test  

Third party testing  

By operation or not  

The static test

Dynamic testing  

Manually divided by  

Manual testing

automated testing  


By test object

Interface tests

The interface interacts directly with the user , The quality of interface design determines the user's intuitive feeling of using the software

UI test

  • Make sure the interface and UI Consistency of design draft , correctness
  • Test the correctness of each function of the interface ( From top to bottom , From left to right )
  • The interface layout is reasonable ( font size , Picture layout , Clarity )
  • Whether the control function of the interface is normal ( Scroll bar , Button , The text box )
  • Test the interface with different resolution
  1. The page changes from small to large, and the connection is smooth , Make it acceptable to users
  2. The font of the page is not blurred and does not disappear , No ghosting
  3. Page image does not disappear , The layout is reasonable
  4. Page function can be used normally

Reliability test

reliability Ready to use , It refers to the ability or degree of normal operation of the system , Generally, software services are provided to users in normal mode As a percentage of the total time .

reliability = Normal operation time /( Normal operation time + Abnormal operation time )

The abnormal operation time of the system may be due to the hardware , Software , Network failure or any other factor ( Such as power failure ) Caused by the , These factors can stop the system from working , Or the connection is broken and cannot be accessed , Or the service cannot be used due to the sharp performance degradation ( Different systems , The requirements for reliability are different ) 

Fault tolerance test  

Fault tolerance test means that the system can handle exceptions , The wrong operation of the user will not cause the system to crash , Thus, the availability of the system can be improved .
such as : Enter account 6~16 position , At most, you can only input 16 position , To the first 17 You can't lose ; Two passwords are required for registration , And check the consistency of the information before and after . power failure , Broken net ( Artificial system failure ), Test whether the system can recover stability quickly .

Document the test  

file : Various documents generated in the whole development process , The requirements document , Design document , Function document , User manual

The focus of document testing :

The correctness of the document , Uniformity , integrity , Professional term , Ease of use

  Compatibility test

  • Platform compatibility :web Webpage ( Various browsers , The compatibility of the operating system )APP:( Different systems (IOS/Android), Different brands , Different system versions )
  • Software compatibility : The compatibility of the software with its own functions , For example, the new functions developed cannot affect the old functions , Nor can it affect the development of subsequent functions .
  • Software compatibility with third-party software : It shall not affect the use of other software ; If you interact with third-party software , Data must be compatible .

Ease of use test

  Ease of use consists of seven elements : Comply with standards and specifications , Intuitiveness , Uniformity , flexibility , comfort , Correctness and practicability .

Standardization and standardization  

All kinds of information on the user interface should conform to the specifications and habits , Otherwise, users will be uncomfortable , Not recognized by users . The tester needs to compare with the standard specification , Habit inconsistency problems are reported as defects .

Intuitiveness  

Intuitive user interface , It is required that the software functional features are easy to understand , Clear . The user interface layout is reasonable , The response to the operation is expected by the user .

flexibility  

The software can have different options to satisfy users with different usage habits to complete the same functions . For example, the mobile phone keyboard has nine squares and a full keyboard , Handwriting is also supported , Meet the needs of different users .

comfort

Comfort mainly emphasizes friendly interface , beautiful , The operation process is smooth , Colors are used properly , The stereoscopic feeling of the button, etc . Make users aware of their own operations , No anxiety .

Install uninstall test

  • The software can be installed and uninstalled normally
  • Software update
  • install / uninstall Under abnormal conditions such as network disconnection and power failure during software operation , Software response
  • If the memory of the installation software is insufficient, whether there is a prompt
  • Uninstall software pause , Can I continue uninstalling
  • Uninstall the software to half , Cancel uninstall , See if the software can be used normally
  • Whether the data file information of the software after uninstallation is cleaned

Security testing  

Security refers to information security , It refers to the protection of user data privacy by computer system or network , complete , Protect the normal transmission of data and resist hackers , Ability of virus attack .
Anti virus , Anti hacker attacks , prevent xss Inject ,SQL Inject , Anti reptile

Performance testing  

Performance problems of software products , Analyze the performance requirements of the product , Then based on the system performance requirements and system architecture , Complete the design and implementation of performance test , Finally, continuous performance tuning .
Common performance problems are as follows :
  • Memory leak
  • Resource bottleneck
  • The system is running slower and slower
  • The operation of the system is more and more affected by the outside world
  • thread deadlock , Thread blocking
  • Inquire about , Loading information is slow

Memory leak test  

Memory leaks can cause the system to run more and more slowly

Cause :

  • After memory allocation , No recycling
  • API Incorrect use of function , It can't be recycled
  • There is a problem with memory allocation , It can't be recycled

By whether or not to view code  

Black box testing

Don't care about software implementation , Do not care about the logical structure of the program , Only care about whether the input and output of software functions are symbolic requirements ( Only pay attention to the function of the software )

Black box test method

Equivalence class , The boundary value , Cause and effect diagram , Orthogonal hair , Wrong guess , Scene method

White box testing

Test the realization of software functions , Test the style of the implementation code , Logic , structure , Design , See if the required functions have been implemented ( It mainly tests the code )

Test method of white box test

Statement override , Path coverage , Determine coverage , Conditional coverage , Determine the combination , Conditional combination , Decision and condition combination , Cycle coverage

Test method : unit testing ,java,Junit

Grey box testing

Between white box test and black box test , Grey box testing is mostly used in the integration testing stage , It's not just about output 、 The correctness of the input , At the same time, we also pay attention to the internal situation of the program .

By development stage

unit testing

The test method : White box testing

Test content : Module interface test , Local data structure test , Boundary test , Error exception test , Path test

Integration testing  

The test method : Grey box testing

Test content : The interface between modules , Whether the functions of different modules conflict , Functions of the whole module , Global data structure test , The impact of defects in a single module on this module

The system test  

The test method : Black box testing

Test content : Interface tests , A functional test , Reliability test , Portability testing , Compatibility test , Security testing , Fault tolerance test , Install the uninstall , Performance etc.

regression testing

Regression testing is when you modify old code , Retest to make sure that the changes do not introduce new errors or cause errors in other code .

Smoke testing

The object of smoke test is every newly compiled software version that needs to be formally tested , The purpose is to confirm that the main functions and core processes of the software are normal , Execute before the formal system test . Smoke tests are generally submitted to testers for testing after developers' development , Smoke test first , Make sure the basic function is normal , Do not hinder subsequent testing .
Regression test and smoke test belong to system test

The acceptance test

The test method : Black box testing

Test content : Same as system test , Including document testing

Testers : Users or end users

Divided by test implementation organization  

α test

α Testing is a test conducted by a user in the development environment , It can also be a test conducted by users inside the company under simulated actual operating environment . Developers and testers are not involved .

β test  

β Testing is an acceptance test .β Testing is carried out by end users of the software in one or more places .

α Test and β Test differences :

  • The test site is different ,α Testing is to invite users to the developer's place to test ,β Testing refers to the testing conducted at the site of one or more users  .
  • α The test environment is controlled by the developer , The number of users is relatively small , Time is more concentrated .β The testing environment is not controlled by the developer , The number of users is relatively large , Time is not concentrated .
  • α Testing takes precedence over β The test is performed first

Third party testing  

Organizational testing between developers and users .

By operation or not  

The static test

The static test Namely Not actually running Software under test , But only Check the program code statically 、 Interface or document Possible errors in the process .

Dynamic testing  

Dynamic testing , refer to Actually run the program under test , Input the corresponding test data , Check the actual output Whether it is consistent with the expected results The process of .

Manually divided by  

Manual testing

Manual testing is that people enter use cases one by one , And then observe the results , Corresponding to machine testing , It belongs to a relatively primitive but necessary step .
advantage : Automation cannot replace exploratory testing 、 A test of the results of divergent thinking .
shortcoming : Slow execution , A large quantity is easy to make mistakes

automated testing  

Automated testing is running a system or application under preset conditions , Evaluate the operation results , Preconditions should include normal and abnormal conditions . In short, automated testing is a process that transforms human driven testing behavior into machine execution .
Not all projects are suitable for automated testing , Automated testing is not suitable for unstable projects , Items whose functions change frequently  
原网站

版权声明
本文为[Pinellia tuber is cool]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/172/202206212032450431.html