![테스트 자동화의 원칙 김태우 [email_address] 아꿈사 http://café.naver.com/architect1](https://image.slidesharecdn.com/random-100730200900-phpapp02/85/-1-320.jpg)
![개요 ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à 테스트 자동화의 원칙
Similaire à 테스트 자동화의 원칙 (20)
Plus de codevania
테스트 자동화의 원칙
- 1. 테스트 자동화의 원칙 김태우 [email_address] 아꿈사 http://café.naver.com/architect1
Notes de l'éditeur
- Concise As simple as possible and no simpler. Self Checking Test reports its own results; needs no human interpretation. Repeatable Test can be run many times in a row without human intervention. Robust Test produces same result now and forever. Tests are not affected by changes in the external environment. Sufficient Tests verify all the requirements of the software being tested. Necessary Everything in each test contributes to the specification of desired behavior. Clear Every statement is easy to understand Efficient Tests run in a reasonable amount of time. Specific Each test failure points to a specific piece of broken functionality; unit test failures provide "defect triangulation" Independent Each test can be run by itself or in a suite with an arbitrary set of other tests in any order. Maintainable Tests should be easy to understand and modify and extend. Traceable To and from the code it tests and to and from the requirements.
- 테스트 별로 하나의 조건만 검증하라는 원칙에 있어 반드시 하나의 단언문만 있어야 한다고 주장하고 싶진 않다 .