일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | ||
6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 14 | 15 | 16 | 17 | 18 | 19 |
20 | 21 | 22 | 23 | 24 | 25 | 26 |
27 | 28 | 29 | 30 | 31 |
- streamlit
- 스프링 부트3
- openai
- 쓰레드 풀
- 셀레니움
- 파이썬
- 오라클
- conda remove
- 컬렉션 프레임웍
- db
- 사이킷런
- 알고리즘
- 사이킷런 회귀
- 프로그래머스
- 머신러닝
- 완주하지못한선수
- WinError5
- 자바 로그 레벨
- 차원증가
- 컬렉션 인터페이스
- URI 원칙
- h2 데이타베이스
- REST API
- 자바 열거형
- oracle
- Python
- GIT
- Java
- Selenium
- 스프링 부트
- Today
- Total
노트 :
테스트주도개발(TDD, Test-driven Development) 본문
Test-driven development (TDD) is a software development process relying on software requirements being converted to test cases before software is fully developed, and tracking all software development by repeatedly testing the software against all test cases. This is as opposed to software being developed first and test cases created later. Test-driven development is related to the test-first programming concepts of extreme programming, begun in 1999, but more recently has created more general interest in its own right.
1. TDD cycle
① Add a test
② Run all tests. The new test should fail for expected reasons
③ Write the simplest code that passes the new test
④ All tests should now pass
⑤ Refactor as needed
2. concept expansion: Test-driven Work
① "Add a check" replaces "Add a test"
② "Run all checks" replaces "Run all tests"
③ "Do the work" replaces "Write some code"
④ "Run all checks" replaces "Run tests"
⑤ "Clean up the work" replaces "Refactor code"
⑥ "Repeat"
source: wikipedia
'자격증' 카테고리의 다른 글
관계대수 및 관계해석 (0) | 2023.02.07 |
---|---|
Secure SDLC (0) | 2023.02.06 |
트러스트존 기술(TrustZone Technology) (0) | 2023.02.06 |
기억장치 (0) | 2023.02.05 |
프로세스 제어 블록(PCB), 파일 제어 블록(FCB) (0) | 2023.02.05 |