测试类型 2

51. Gorilla Testing (Gorilla 测试): Gorilla Testing is a type of software testing done by software testing team, has a scary name though Objective of Gorilla Testing is to exercise one or few functionality thoroughly or exhaustively by having multiple people test the same functionality.

52. Hybrid Integration Testing (Hybrid 整合测试): Also known as sand witch testing is a combination of both bottom up and top down integration testing techniques. By combining both of these once can find more defects at the same time provide better integration test coverage.

53. Happy path testing (Happy 路经测试): Also known as Golden path testing, this type of testing focuses on selective execution of tests that do not exercise the software for negative or error conditions.

54. Integration Testing (整合测试): Integration testing also known as I&T in short, in one of the important types of software testing. Once the individual units or components are tested by developers as working then testing team will run tests that will test the connectivity among these units/component or multiple units/components. There are different approaches for Integration testing namely, Top-down integration testing, Bottom-up integration testing and a combination of these two known as Sand witch testing.

55. Interface Testing (接口测试): Software provides support for one or more interfaces like “Graphical user interface“, “Command Line Interface“ or “Application programming interface“ to interact with its users or other software. Interfaces serves as medium for software to accept input from user and provide result. Approach for interface testing depends on the type of the interface being testing like GUI or API or CLI.

56. Internationalization Testing (国际化测试): Internationalization testing is a type of testing that is performed by software testing team to check the extent to which software can support Internationalization i.e., usage of different languages, different character sets, double byte characters etc., For e.g.: Gmail, is a web application that is used by people all over work with different languages, single by or multi byte character sets.

57. I18n Testing (I18n 测试): I18n refers toInternationalization Testing, in the word “Internationalization“, between letters “I“ and “n“ there are about 18 letters, hence the name i18n.

58. Installation/un-installation Testing (安装/卸载测试): Installation/un-installation Testing is a type of testing performed by testing team to find defects related to installation and un-installation of software. This type of testing is very important for packaged software applications (off the shelf software applications) where-in end users are expected to install the software. This testing would involve executing software installer in different modes like “express“ or “custom“ modes and on different types of environments like virtual operating systems and on different operating systems. Installation/un-installation Testing may also require updating software configuration files.

59. Keyword-driven Testing (关键驱动测试): Keyword driver testing is more of a automated software testing approach than a type of testing itself. Keyword driven testing is known as action driven testing or table driven testing.

60. Load Testing (负载测试): Load testing is a type of non-functional testing; load testing is done to check the behavior of the software under normal and over peak load conditions. Load testing is usually performed using automated testing tools. Load testing intends to find bottlenecks or issues that prevent software from performing as intended at its peak workloads.

61. Localization Testing (本地化测试): Localization testing a type of software testing performed by software testers, in this type of testing, software is expected to adapt to a particular locale, it should support a particular locale/language in terms of display, accepting input in that particular locale, display, font, date time, currency etc., related to a particular locale. For e.g. many web applications allow choice of locale like English, French, German or Japanese. So once locale is defined or set in the configuration of software, software is expected to work as expected with a set language/locale.

62. Loop Testing (循环测试): Loop testing is a type of white box testing technique, it is one of the most commonly used white box testing technique while performing unit testing.

63. Monkey testing (猴子测试): Monkey testing is a type of testing that can be performed by software testing team or new users of the software. Objective of monkey testing is to use the software without any specific tests in mind. Monkey test tries to break the software by entering incorrect dates like 31-Feb-2012 or long strings of text or numbers or special characters etc.,

64. Negative Testing (负面测试): is a type of software testing approach, which calls out the “attitude to break“, these are functional and non-functional tests that are intended to break the software by entering incorrect data like incorrect date, time or string or upload binary file when text files supposed to be upload or enter huge text string for input fields etc.,

65. Non functional testing (非功能测试): Software are built to fulfill functional and non-functional requirements, non-functional requirements like performance, usability, localization etc., There are many types of testing like compatibility testing, compliance testing, localization testing, usability testing, volume testing etc., that are carried out for checking non-functional requirements.

66. ORT (Operational readiness testing) (运行状态测试): Operational readiness testing also known as pre go live testing is usually performed by software testers. As the name suggests, Operational readiness testing intends to validate the production environment after new version of the software is deployed in production environment. Software testers test the existing and new functionality to certify that the software is ready to be used by end users.

67. Orthogonal array Testing (正交阵列测试): is a black box testing technique. Orthogonal array Testing is statistical and systematic way of Software testing. Orthogonal array Testing technique helps to minimize the number of test cases and maximize test coverage by grouping set of test conditions. Orthogonal testing is effective in case of GUI testing, Configuration testing where there are multiple input parameters and testing one parameter at a time would lead to large number of test cases.

68. Pair Testing (成对测试): is a software testing technique that can be done by software testers, developers or Business analysts (BA). As the name suggests, two people are paired together, one to test and other to monitor and record test results. Pair testing can also be performed in combination of tester-developer, tester-business analyst or developer-business analyst combination. Combining testers and developers in pair testing helps to detect defects faster, identify root cause, fix and test the fix.

69. Parallel Testing (并行测试): is a software testing technique, where in you test two or more versions of the software “the current version“ and “previous version or versions“ of the software together to see the differences of existing functionality.

70. Path Testing (路经测试): is a type of software testing technique that is used as part of white box testing approach. Objective of path testing is to exercise and test each of the branch statements. These testing techniques are applied by developers while performing Unit testing.

71. Performance Testing (性能测试): is a type of software testing and part of performance engineering that is performed to check some of the quality attributes of software like Stability, reliability, availability. Performance testing is carried out by performance engineering team. Unlike Functional testing, Performance testing is done to check non-functional requirements. Performance testing checks how well software works in anticipated and peak workloads. There are different variations or sub types of performance like load testing, stress testing, volume testing, soak testing and configuration testing.

72. Penetration Testing (渗透测试): is a type of security testing, also known as pentest in short. Penetration testing is done to tests how secure software and its environments (Hardware, Operating system and network) are when subject to attack by an external or internal intruder. Intruder can be a human/hacker or malicious programs. Pentest uses methods to forcibly intrude (by brute force attack) or by using a weakness (vulnerability) to gain access to a software or data or hardware with an intent to expose ways to steal, manipulate or corrupt data, software files or configuration. Penetration Testing is a way of ethical hacking, an experienced Penetration tester will use the same methods and tools that a hacker would use but the intention of Penetration tester is to identify vulnerability and get them fixed before a real hacker or malicious program exploits it.

73. Ramp Testing (斜坡测试): is a type of testing conducted to check the response of the software with constant increase in workload on the software. Ramp testing enables tests the ability of the software to sustain gradual increase in work load.

74. Regression Testing (回归测试): is a type of software testing that is carried out by software testers as functional regression tests and developers as Unit regression tests. Objective of regression tests are to find defects that got introduced to defect fix(es) or introduction of new feature(s). Regression tests are ideal candidate for automation.

75. Retesting (重新测试): is a type of retesting that is carried out by software testers as a part of defect fix verification. For e.g. a tester is verifying a defect fix and let us say that there are 3 test cases failed due to this defect. Once tester verifies defect fix as resolved, tester will retest or test the same functionality again by executing the test cases that were failed earlier.

76. Resilience testing (恢复测试): is a type of testing carried by performance engineering team to assess how stable the software is when it is subject to incorrect data, large workloads and more volume of data to be processes.

77. Recovery Testing (恢复测试): is a type of testing performed by software testers. Recovery testingaims at checking how soon and how efficiently software can recover from software crashes, Operating system crashers, and hardware failures. Recovery testing is not the same as fail rover testing or reliability testing.

78. Risk based Testing (风险测试): is a type of software testing and an different approach towards testing a software. In Risk based testing, requirements and functionality of software to be tested are prioritized as Critical, High, Medium and low. In this approach, all critical and High priority tests are tested and them followed by Medium. Low priority or low risk functionality are tested at the end or may not based on the time available for testing.

79. Smoke testing (冒烟测试): is a type of testing that is carried out by software testers to check if the new build provided by development team is stable enough i.e., major functionality is working as expected in order to carry out further or detailed testing. Smoke testing is intended to find “show stopper“ defects that can prevent testers from testing the application in detail. Smoke testing carried out for a build is also known as build verification test.

80. Security Testing (安全性测试): is a type of software testing carried out by specialized team of software testers. Objective of security testing is to secure the software is to external or internal threats from humans and malicious programs. Security testing basically checks, how good is software‘s authorization mechanism, how strong is authentication, how software maintains confidentiality of the data, how does the software maintain integrity of the data, what is the availability of the software in an event of an attack on the software by hackers and malicious programs is for Security testing requires good knowledge of application, technology, networking, security testing tools. With increasing number of web applications necessarily of security testing has increased to a greater extent.

81. Sanity Testing (健全性测试): is a type of testing that is carried out mostly by testers and in some projects by developers as well. Sanity testing is a quick evaluation of the software, environment, network, external systems are up & running, software environment as a whole is stable enough to proceed with extensive testing. Sanity tests are narrow and most of the time sanity tests are not documented.

82. Scalability Testing (可扩展性测试): is anon functional test intended to test one of the software quality attributes i.e. “Scalability“. Scalability test is not focused on just one or few functionality of the software instead performance of software as a whole. Scalability testing is usually done by performance engineering team. Objective of scalability testing is to test the ability of the software to scale up with increased users, increased transactions, increase in database size etc., It is not necessary that software’s performance increases with increase in hardware configuration, scalability tests helps to find out how much more workload the software can support with expanding user base, transactions, data storage etc.,

83. Stability Testing (稳定性测试): is a non functional test intended to test one of the software quality attributes i.e. “Stability“. Stability testing focuses on testing how stable software is when it is subject to loads at acceptable levels, peak loads, loads generated in spikes, with more volumes of data to be processed. Scalability testing will involve performing different types of performance tests like load testing, stress testing, spike testing, soak testing, spike testing etc.,

84. Structural testing (结构测试): is an alias for White box testing. Refer to white box testing for more details.

85. Static Testing (静态测试): is a form of testing where in approaches like reviews, walkthroughs are employed to evaluate the correctness of the deliverable. In static testing software code is not executed instead it is reviewed for syntax, commenting, naming convention, size of the functions and methods etc. Static testing usually has check lists against which deliverables are evaluated. Static testing can be applied for requirements, designs, test cases by using approaches like reviews or walkthroughs.

86. Stress Testing (负载测试):Stress Testing is a type of performance testing, in which software is subjected to peak loads and even to a break point to observe how the software would behave at breakpoint. Stress testing also tests the behavior of the software with insufficient resources like CPU, Memory, Network bandwidth, Disk space etc. Stress testing enables to check some of the quality attributes like robustness and reliability.

87. System Testing (系统测试): this includes multiple software testing types that will enable to validate the software as a whole (software, hardware and network) against the requirements for which it was built. Different types of tests (GUI testing, Functional testing, Regression testing, Smoke testing, load testing, stress testing, security testing, stress testing, ad-hoc testing etc.,) are carried out to complete system testing.

88. Soak Testing (稳定性测试): is a type ofperformance testing, where in software is subjected to load over a significant duration of time, soak testing may go on for few days or even for few weeks. Soak testing is a type of testing that is conducted to find errors that result in degeneration of software performance with continued usage. Soak testing is extensively done for electronic devices, which are expected to run continuously for days or months or years without restarting or rebooting. With growing web applications soak testing has gained significant importance as web application availability is critical for sustaining and success of business.

89. Spike Testing (脉冲测试): is a type ofperformance testing performed by performance engineering team. Objective of spike testing is to check how software responds to workloads that are sent in very short span of time and which are not constant over period of time.

90. System Integration Testing (系统整合测试): known as SIT (in short) is a type of testing conducted by software testing team. As the name suggests, focus of System integration testing is to test for errors related to integration among different applications, services, third party vendor applications etc., As part of SIT, end-to-end scenarios are tested that would require software to interact (send or receive data) with other upstream or downstream applications, services, third party application calls etc.,

91. Transparent box testing (透明测试): is an alias for White box testing. Refer to White box Testingfor more details.

92. Top down Integration testing (自上而下整合测试): is one of the integration testingapproaches. Top down integration testing is an incremental testing approach for integration testing where in testing of top level modules are done first before moving on to testing of branch modules. Top down integration testing helps to find design issues in the beginning of the Integration test stage.

93. Upgrade testing (升级测试): is a type of testing that is carried out by software testers. Upgrade testing is more often carried out after an hardware upgrade or operating system upgrade or any other supporting software like JVM or Web server or application server. For e.g. if JRE is upgraded from 1.0 to 2.3.3 then the subset of the functional tests have to be executed to ensure application features are not broken due to JRE upgrade.

94. Unit testing (单元测试): Unit testing is a type of testing that is performed by software developers. Unit testing follows white box testing approach where developer will test units of source code like statements, branches, functions, methods OR class, interface in OOP (object oriented programming). Unit testing usually involves in developing stubs and drivers. Unit tests are ideal candidates for automation. Automated tests can run as Unit regression tests on new builds or new versions of the software. There are many useful unit testing frames works like Junit, Nunit etc., available that can make unit testing more effective.

95. Upward compatibility Testing (向上兼容性测试): Upward compatibility testing is another name for forward compatibility Testing.

96. Usability testing (可用性测试): is a type of software testing that is performed to understand how user friendly the software is. Objective of usability testing is to allow end users to use the software, observe their behavior, their emotional response (whether users liked using software or were they stressed using it? etc.,) and collect their feedback on how the software can be made more useable or user friendly and incorporate the changes that make the software easier to use.

97. User Acceptance testing (UAT ) (用户验收测试 ): User Acceptance testing is a must for any project; it is performed by clients/end users of the software. User Acceptance testing allows SMEs (Subject matter experts) from client to test the software with their actual business or real-world scenarios and to check if the software meets their business requirements.

98. Volume testing (性能测试): is a non-functional type of testing carried out by performance engineering team. Volume testing is one of the types of performance testing. Volume testing is carried out to find the response of the software with different sizes of the data being received or to be processed by the software. For e.g. If you were to be testing Microsoft word, volume testing would be to see if word can open, save and work on files of different sizes (10 to 100 MB).

99. Vulnerability Testing (漏洞测试): involves identifying, exposing the software, hardware or network Vulnerabilities that can be exploited by hackers and other malicious programs likes viruses or worms. Vulnerability Testing is key to software security and availability. With increase number of hackers and malicious programs, Vulnerability Testing is critical for success of a Business.

100. White box Testing (白盒测试): White box testing is also known as clear box testing, transparent box testing and glass box testing. White box testing is a software testing approach, which intends to test software with knowledge of internal working of the software. White box testing approach is used in Unit testing which is usually performed by software developers. White box testing intends to execute code and test statements, branches, path, decisions and data flow within the program being tested. White box testing and Black box testing complement each other as each of the testing approaches have potential to un-cover specific category of errors.