소프트웨어 테스팅

소프트웨어 테스팅에는 다음과 같은 26가지가 있다고 한다. 각각의 테스트에 대한 더 자세한 설명은 엮인글을 참고하기 바란다.
복귀시험(Regression testing)-뭔가 고치고 나서 되던게 잘되는 지 확인하는 시험
수락시험(Acceptance testing)-스펙에 기반한 시험
부하시험(Load testing)-부하가 어떤 성능에 차이를 보이는가를 알아보는 시험
과부하시험(Stress testing)-과부하에서의 시험
성능시험(Performance testing)-요구사항문서에 정의하는 성능을 시험
사용성시험(Usability testing)-사용자 편의성 시험
설치삭제시험(Install/uninstall testing)-설치,삭제,업그레이드시험
복구시험(Recovery testing)-에러,실패등에서 얼마나 잘 복구되는가 시험
보안시험(Security testing)-비인가된 내,외부의 접근에 대한 방호기능 시험
기능시험(Functional testing)-기능요구사항에 기반한 동작시험
시스템시험(System testing)-전체요구사항에 기반한 동작시험
종단간시험(End-to-end testing)-실제주변시스템과 연동시험
온전시험(Sanity testing)-문제점위주의 시험
블랙박스시험(Black box testing)-내부구조를 모르는 상황에서의 요구사항에 기반한 시험
화이트박스시험(White box testing)-내부로직을 고려하여, 코드의 제어흐름을 시험
단위시험(Unit testing)-코드나 모듈의 일부만 시험
점층적통합시험(Incremental integration testing)-새로운 기능이 추가됨에 따른 계속적인 시험.
통합시험(Integration testing)-각 부분들을 통합한 후의 시험
호환시험(Compatibility testing)-다른 것들과 호환시험
탐사시험(Exploratory testing)-이것저것해보는 시험. (소프트웨어의 내부를 알아낼 수 있다)
임시시험(Ad-hoc testing)-소프트웨어내부를 알고 있으면서, 이것저것해보는 시험
사용자수락시험(User acceptance testing)-소프트웨어가 최종사용자 및 고객에 만족스러운지 여부를 결정하는 시험
비교시험(Comparison testing)-경쟁사제품과 비교시험
알파테스트(Alpha testing)-개발이 거의 끝났을 때, 사용자 위주로 시험
베타테스트(Beta testing)-기본적인 개발이 끝나고, 버그를 잡기 위한 시험
전환시험(Mutation testing)-테스트방법,시험데이터가 유효한지 확인하는 시험



>접기

(엮인글을 퍼왔습니다)

• Regression testing - re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

• Acceptance testing - final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.

• Load testing - testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.

• Stress testing - term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.

• Performance testing - term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.

• Usability testing - testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.

• Install/uninstall testing - testing of full, partial, or upgrade install/uninstall processes.

• Recovery testing - testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

• Security testing - testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.

• Functional testing - black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)

• System testing - black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.

• End-to-end testing - 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, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

• Sanity testing - typically 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.

• Black box testing - not based on any knowledge of internal design or code. Tests are based on requirements and functionality.

• White box testing - based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.

• Unit testing - the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.

• Incremental integration testing - continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.

• Integration testing - testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

• Compatibility testing - testing how well software performs in a particular hardware/software/operating system/network/etc. environment.

• Exploratory testing - often taken to mean a 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.

• Ad-hoc testing - similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.

• User acceptance testing - determining if software is satisfactory to an end-user or customer.

• Comparison testing - comparing software weaknesses and strengths to competing products.

• Alpha testing - testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

• Beta testing - testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

• Mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.