SlideShare a Scribd company logo
测试快照 Testing snapshot
[object Object],[object Object],[object Object],1 ,单元测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],2 ,白盒测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],3 ,黑盒测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],4 ,集成测试
[object Object],[object Object],[object Object],5 ,增量集成测试
[object Object],[object Object],[object Object],[object Object],6 ,系统测试
[object Object],[object Object],[object Object],7 ,功能测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],8 ,端到端的测试
[object Object],[object Object],[object Object],9 ,阿尔法测试
[object Object],[object Object],[object Object],[object Object],10 ,贝塔测试
[object Object],[object Object],[object Object],11 ,验收测试
[object Object],[object Object],[object Object],12 ,回归测试
[object Object],[object Object],[object Object],13 ,性能测试
[object Object],[object Object],[object Object],14 ,负载测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],15 ,压力测试
[object Object],[object Object],[object Object],16 ,比较测试
[object Object],[object Object],17 ,健全测试
[object Object],[object Object],[object Object],18 ,可用性测试
[object Object],[object Object],19 ,安装 / 卸载测试
[object Object],[object Object],20 ,恢复测试
[object Object],[object Object],[object Object],[object Object],21 ,探索性测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],22 ,兼容性测试
[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],23 ,随机测试
[object Object],[object Object],24 ,变异测试
[object Object],[object Object],25 ,安全测试
… … … …

More Related Content

What's hot

例外處理實務
例外處理實務例外處理實務
例外處理實務
Jeff Chu
 
PHPUnit
PHPUnitPHPUnit
PHPUnit
jameslabs
 
Qa engineer training
Qa engineer trainingQa engineer training
Qa engineer training
ychw365
 
前端单元测试
前端单元测试前端单元测试
前端单元测试LC2009
 
论文:基于Android设备的音视频实时监控系统的设计与实现130826
论文:基于Android设备的音视频实时监控系统的设计与实现130826论文:基于Android设备的音视频实时监控系统的设计与实现130826
论文:基于Android设备的音视频实时监控系统的设计与实现130826
Shawn Zhung
 
测试用例浅析 V1.1
测试用例浅析 V1.1测试用例浅析 V1.1
测试用例浅析 V1.1shijian_dev
 
基于Android设备的音视频实时监控系统的设计与实现
基于Android设备的音视频实时监控系统的设计与实现基于Android设备的音视频实时监控系统的设计与实现
基于Android设备的音视频实时监控系统的设计与实现
Shawn Zhung
 
Duannian agile
Duannian agileDuannian agile
Duannian agiled0nn9n
 

What's hot (8)

例外處理實務
例外處理實務例外處理實務
例外處理實務
 
PHPUnit
PHPUnitPHPUnit
PHPUnit
 
Qa engineer training
Qa engineer trainingQa engineer training
Qa engineer training
 
前端单元测试
前端单元测试前端单元测试
前端单元测试
 
论文:基于Android设备的音视频实时监控系统的设计与实现130826
论文:基于Android设备的音视频实时监控系统的设计与实现130826论文:基于Android设备的音视频实时监控系统的设计与实现130826
论文:基于Android设备的音视频实时监控系统的设计与实现130826
 
测试用例浅析 V1.1
测试用例浅析 V1.1测试用例浅析 V1.1
测试用例浅析 V1.1
 
基于Android设备的音视频实时监控系统的设计与实现
基于Android设备的音视频实时监控系统的设计与实现基于Android设备的音视频实时监控系统的设计与实现
基于Android设备的音视频实时监控系统的设计与实现
 
Duannian agile
Duannian agileDuannian agile
Duannian agile
 

Similar to 测试快照

软件工程 第七章
软件工程 第七章软件工程 第七章
软件工程 第七章浒 刘
 
使用 Pytest 進行單元測試 (PyCon TW 2021)
使用 Pytest 進行單元測試 (PyCon TW 2021)使用 Pytest 進行單元測試 (PyCon TW 2021)
使用 Pytest 進行單元測試 (PyCon TW 2021)
Max Lai
 
Foundation of software development 1
Foundation of software development 1Foundation of software development 1
Foundation of software development 1netdbncku
 
有效的单元测试.ppt
有效的单元测试.ppt有效的单元测试.ppt
有效的单元测试.ppt
test499702
 
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
Rick Hwang
 
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
Gelis Wu
 
Foundation of software development 2
Foundation of software development 2Foundation of software development 2
Foundation of software development 2netdbncku
 
Static Code Analysis 靜態程式碼分析
Static Code Analysis 靜態程式碼分析Static Code Analysis 靜態程式碼分析
Static Code Analysis 靜態程式碼分析
Bill Lin
 
分布式系统测试实践
分布式系统测试实践分布式系统测试实践
分布式系统测试实践drewz lin
 
Web testing automation
Web testing automationWeb testing automation
Web testing automation
kuozui
 
調試器原理與架構
調試器原理與架構調試器原理與架構
調試器原理與架構hackstuff
 
系統05_從持續整合結合安全開發與變更管理 郭俐佳
系統05_從持續整合結合安全開發與變更管理 郭俐佳系統05_從持續整合結合安全開發與變更管理 郭俐佳
系統05_從持續整合結合安全開發與變更管理 郭俐佳
Galaxy Software Services
 
网站前端代码静态检查工具综述
网站前端代码静态检查工具综述网站前端代码静态检查工具综述
网站前端代码静态检查工具综述pop2008
 
How+we+make+tests
How+we+make+testsHow+we+make+tests
How+we+make+tests甘 李
 
Unit test
Unit testUnit test
Unit test
shan chen
 
加密方案设计原则
加密方案设计原则加密方案设计原则
加密方案设计原则
nncbqqcom
 
广告技术部自动化测试介绍.pdf
广告技术部自动化测试介绍.pdf广告技术部自动化测试介绍.pdf
广告技术部自动化测试介绍.pdfbj_qa
 
PHPUnit slide formal
PHPUnit slide formalPHPUnit slide formal
PHPUnit slide formaljameslabs
 

Similar to 测试快照 (20)

软件工程 第七章
软件工程 第七章软件工程 第七章
软件工程 第七章
 
使用 Pytest 進行單元測試 (PyCon TW 2021)
使用 Pytest 進行單元測試 (PyCon TW 2021)使用 Pytest 進行單元測試 (PyCon TW 2021)
使用 Pytest 進行單元測試 (PyCon TW 2021)
 
Foundation of software development 1
Foundation of software development 1Foundation of software development 1
Foundation of software development 1
 
有效的单元测试.ppt
有效的单元测试.ppt有效的单元测试.ppt
有效的单元测试.ppt
 
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
從理想、到現實的距離,開啟品味軟體測試之路 - 台灣軟體工程協會 (20220813)
 
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
Visual studio 2012 與 asp.net 4.5 (新功能與開發介紹) 第四天
 
Foundation of software development 2
Foundation of software development 2Foundation of software development 2
Foundation of software development 2
 
Xpp
XppXpp
Xpp
 
Static Code Analysis 靜態程式碼分析
Static Code Analysis 靜態程式碼分析Static Code Analysis 靜態程式碼分析
Static Code Analysis 靜態程式碼分析
 
分布式系统测试实践
分布式系统测试实践分布式系统测试实践
分布式系统测试实践
 
Web testing automation
Web testing automationWeb testing automation
Web testing automation
 
調試器原理與架構
調試器原理與架構調試器原理與架構
調試器原理與架構
 
系統05_從持續整合結合安全開發與變更管理 郭俐佳
系統05_從持續整合結合安全開發與變更管理 郭俐佳系統05_從持續整合結合安全開發與變更管理 郭俐佳
系統05_從持續整合結合安全開發與變更管理 郭俐佳
 
网站前端代码静态检查工具综述
网站前端代码静态检查工具综述网站前端代码静态检查工具综述
网站前端代码静态检查工具综述
 
How+we+make+tests
How+we+make+testsHow+we+make+tests
How+we+make+tests
 
Unit test
Unit testUnit test
Unit test
 
加密方案设计原则
加密方案设计原则加密方案设计原则
加密方案设计原则
 
广告技术部自动化测试介绍.pdf
广告技术部自动化测试介绍.pdf广告技术部自动化测试介绍.pdf
广告技术部自动化测试介绍.pdf
 
jasmine入门指南
jasmine入门指南jasmine入门指南
jasmine入门指南
 
PHPUnit slide formal
PHPUnit slide formalPHPUnit slide formal
PHPUnit slide formal
 

测试快照

Editor's Notes

  1. Unit Testing The most ‘micro’ scale of testing that is used for function or code testing. A code walkthrough is to be performed before the unit test. May require developing test driver modules or test harnesses.
  2. Whitebox Testing Based on knowledge of the internal logic of an application’s code. Tests are based on coverage of code statements, branches, paths, conditions. Various types are: Basis Path Testing Loop Testing Input Testing Profiling
  3. Blackbox Testing Done with user perspectives Not based on any knowledge of internal design or code. Tests are based on requirements and functionality The term blackbox refers to ‘Input/Unknown process/Output’ approach to testing (Data or condition driven) Techniques for managing the amount of input data required. Equivalence Partitioning Boundary Analysis Error Guessing
  4. Integration Testing The term refers to orderly progression of testing in which s/w and-or h/w elements are combined and tested until the entire system is tested. This type of testing is especially relevant to client/server or distributed systems. For deciding the order of module integration following approaches may be followed. Top-Level modules Bottom-Level modules Critical modules An so on……..
  5. Incremental Integration Testing The term refers to continuous testing of application as new functionality is added. Requires various aspects of applications functionality to be independent enough to work separately. May require test drivers to be developed.
  6. System Testing It is black box type of testing. It is based on overall requirement specifications; covers all combined parts of a system. It is performed on COTS(Commercial off the shelf) It is based on process description and flow.
  7. Functional Testing This type of testing is geared to functional requirements of an application. It is a black-box type of testing. Should be done by dedicated Testing Team.
  8. End-to-End Testing It is similar to system testing. The ‘macro’ end of the test scale involves testing of a complete application environment in a situation that mimics real-world use. Some of the tests it includes is : Interacting with a database Using network communications Interacting with other hardware, applications, or systems.
  9. Alpha Testing Testing of an application when development is nearing completion; minor design changes may still be made. Typically done by end-users or others, not by programmers. More often this testing is done by the in-house or by an outside testing firm.
  10. Beta Testing Testing of a re-release of a software product. Testing when development and testing are essentially completed Used to find final bugs and problems before final release. Done by end-users or others .
  11. Acceptance Testing It’s the final testing based on specifications of the end-user or customer . Checks that the system delivers what was requested. Done by the customer as he knows what is required from the system.
  12. Regression Testing Retesting after fixes or modifications of the software or its environment . Ensures that system change or new development does not affect unchanged portions of the system. Automated testing tools can be especially useful for this type of testing.
  13. Performance Testing Ideally ‘performance’ testing is defined in requirements documentation or QA or Test Plans. The term performance is often used interchangeably with ’stress’ and ‘load’ testing. It tests the response times and throughput rates under certain workloads and configuration conditions.
  14. Load Testing It is testing an application under heavy loads. Determines at what point the systems response time degrades or fails under a range of loads. Often performed using an automated test tool to simulate large number of users.
  15. Stress Testing The term stress is often used interchangeably with ‘load’ and ‘performance’ testing . Stress testing refers to system functional testing done under heavy load or stresses. The other criteria include Reception of certain actions or input Large complex queries to database system Input of large numerical values, etc
  16. Comparison Testing It is a process of testing that an implementation conforms to the specification and standards. This type of testing includes comparing the software weaknesses and strengths to competing products. Conformance tests should be used by implementers early-on in the development process.
  17. Sanity Testing Sanity Testing is an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a ’sane’ enough condition to warrant further testing in its current state.
  18. Usability Testing Usability testing is ideally for the ‘user-friendliness’. This kind of testing is clearly subjective and depends on the targeted end-user or the customer. User interviews, surveys, video recording of user sessions, and other techniques can be used.
  19. Install/Uninstall Testing This type of testing is performed to ensure that all install features and options function properly. Tests are based on full, partial, or upgrade install/uninstall processes.
  20. Recovery Testing This type of testing is performed for programs having Recovery objectives Tests are based on how well a system recovers from crashes, hardware failures, or other catastrophic problems.
  21. Exploratory Testing Creative, informal software test that is not based on formal test plans or test cases. Testers may be learning the software as they test it Performed whenever the next test you perform is not obvious, or when you want to go beyond the obvious. Especially useful in Complex Testing situations, when little is known about the product, or as part of preparing a set of scripted tests.
  22. Compatibility Testing Carried out to validate proper inter working of interconnecting network facilities & equipment. Performed prior to cutover to validate functional capabilities and services provided over the interconnections. Testing how well software performs in the following environment: Hardware and Software Operating system Network
  23. Ad-hoc Testing A type of quality control testing that operates on randomization rather than on a fixed technique. An exploratory case expected to run only once unless it happens to uncover a defect. Strengths include: Increase in code coverage Check completeness of Testing Determine priorities for other test activities
  24. Mutation Testing A method whereby errors are purposely inserted into a program under test to verify that the test can detect the error. Also known as error seeding.
  25. Security Testing For Security and maintaining the System & Software Integrity. To test how well the system protects against unauthorized internal or external access or willful damage, etc.