Editing
Test-Driven Development
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== The TDD Process === The TDD process typically follows these steps: 1. Write a failing test: Start by writing a test that defines the desired behavior of the code to be implemented. This test should fail initially since the code it is testing doesn't exist yet. 2. Write the minimum amount of code: Write the minimum amount of code required to make the failing test pass. The goal here is to get the test to pass quickly without worrying too much about the quality or completeness of the implementation. 3. Refactor the code: Once the test passes, refactor the code to improve its structure, readability, and maintainability. This step ensures that the code remains clean and concise without introducing any regressions. 4. Repeat: Repeat this cycle by writing the next failing test, implementing the code to pass the test, and refactoring as necessary. This iterative process helps to gradually build up a complete and high-quality codebase.
Summary:
Please note that all contributions to Elixir Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Elixir Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information