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. Software engineer Kent Beck, who is credited with having developed or "rediscovered" the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.
- Comment
- enTest-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. Software engineer Kent Beck, who is credited with having developed or "rediscovered" the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.
- Date
- enFebruary 2022
- Depiction
- Has abstract
- enTest-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. Software engineer Kent Beck, who is credited with having developed or "rediscovered" the technique, stated in 2003 that TDD encourages simple designs and inspires confidence. 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. Programmers also apply the concept to improving and debugging legacy code developed with older techniques.
- Hypernym
- Process
- Is primary topic of
- Test-driven development
- Label
- enTest-driven development
- Link from a Wikipage to an external page
- web.archive.org/web/20130124034916/http:/www.methodsandtools.com/archive/archive.php%3Fid=20
- msdn.microsoft.com/en-us/magazine/cc163665.aspx
- tddconf.com/
- web.archive.org/web/20121021141635/http:/msdn.microsoft.com/en-us/library/ms379625(VS.80).aspx
- www.eiffel.com/general/monthly_column/2004/september.html
- web.archive.org/web/20050209222453/http:/eiffel.com/general/monthly_column/2004/september.html
- Link from a Wikipage to another Wikipage
- .NET Framework
- Acceptance test–driven development
- Acceptance testing
- Apache Ant
- Assertion (computing)
- Atomicity (database systems)
- Behavior-driven development
- C (programming language)
- C2:TestDrivenDevelopment
- Category:Extreme programming
- Category:Software development philosophies
- Category:Software development process
- Category:Software testing
- Code readability
- Code refactoring
- Cohesion (computer science)
- Compliance testing
- Computer network
- Continuous integration
- Continuous test-driven development
- Coupling (computer programming)
- CruiseControl
- Cucumber (software)
- Database
- Database transactions
- Debug
- Debugger
- Dependency injection
- Dependency inversion principle
- Design by contract
- Design pattern
- Directive (programming)
- Dummy code
- Duplicate code
- Exception handling
- Extreme programming
- Fake it till you make it
- File:TDD Global Lifecycle.png
- Fragile tests
- Greenfield project
- Hard code
- Iff
- Inductive programming
- Information hiding
- Inheritance (object-oriented programming)
- Inner class
- Integration testing
- Interface (computer science)
- Java (programming language)
- JBehave
- Kent Beck
- KISS principle
- Legacy code
- Library (computing)
- List of software development philosophies
- List of unit testing frameworks
- Method stub
- Mock object
- Module (programming)
- Mspec
- Name
- NAnt
- Null character
- Object oriented design
- Partial class
- Persistent storage
- Programming by example
- Quality control
- Reflection (computer science)
- Sanity check
- Self-documenting code
- Self-testing code
- Separation of concerns
- Software architecture
- Software bug
- Software development process
- Software quality
- Software requirements
- Software testing
- Specflow
- Specification by example
- Test Anything Protocol
- Test case
- Test double
- Test harness
- Test oracle
- Test suite
- Tracing (software)
- Transformation Priority Premise
- Undo
- Unit testing
- Use case
- User interface
- User story
- Version control system
- XUnit
- You aren't gonna need it
- YouTube
- Reason
- enneeds better explanation, what is an all-knowing oracle? needs better tone, more factual
- SameAs
- 55WPr
- Desarrollo guiado por pruebas
- Desenvolupament guiat per proves
- m.01 2 v
- Phát triển hướng kiểm thử
- Programování řízené testy
- Q950250
- Testdrevet utvikling
- Test driven development
- Test driven development
- Test-driven development
- Test-driven development
- Test-driven development
- Test-driven development
- Test-driven development
- Testdriven utveckling
- Testgetriebene Entwicklung
- Testimisel põhinev arendus
- Testivetoinen kehitys
- Testno voden razvoj
- Tesztvezérelt fejlesztés
- Ανάπτυξη οδηγούμενη από τον έλεγχο (TDD)
- Керована тестами розробка
- Разработка через тестирование
- Разработка чрез тестове
- פיתוח מונחה-בדיקות
- تطوير مقاد بالاختبار
- توسعه آزمونمحور
- テスト駆動開発
- 测试驱动开发
- 테스트 주도 개발
- SeeAlso
- Anti-pattern
- Subject
- Category:Extreme programming
- Category:Software development philosophies
- Category:Software development process
- Category:Software testing
- Thumbnail
- WasDerivedFrom
- Test-driven development?oldid=1123732461&ns=0
- WikiPageLength
- 44930
- Wikipage page ID
- 357881
- Wikipage revision ID
- 1123732461
- WikiPageUsesTemplate
- Template:Cite web
- Template:Clarify
- Template:Columns-list
- Template:More citations needed section
- Template:Reflist
- Template:See also
- Template:Short description
- Template:Software development process
