Editing
TDD
(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!
=== Best Practices for TDD in Elixir === To make the most of TDD in Elixir, consider the following best practices: - '''Keep tests small and focused''': Write tests that are focused on a single unit of functionality to maintain clarity and ease of maintenance. - '''Use descriptive test names''': Clear test names make it easier to understand the intent of the test and facilitate communication among team members. - '''Leverage Elixir's tooling''': Elixir provides powerful test frameworks like ExUnit, which offer a range of features to simplify writing tests and running test suites. - '''Test edge cases and boundaries''': Ensure that tests cover not only typical scenarios but also edge cases, boundary conditions, and error handling to increase the resilience of the code. - '''Continuously run tests''': Automate test execution using tools like mix test.watch to get immediate feedback on changes made to the 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