Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Testing Driven Development (TDD) #61

Open
Adoby7 opened this issue Feb 22, 2019 · 1 comment
Open

Use Testing Driven Development (TDD) #61

Adoby7 opened this issue Feb 22, 2019 · 1 comment
Assignees
@Adoby7
Labels
week 8 week 13

Comments

@Adoby7
Copy link
Contributor

Adoby7 commented Feb 22, 2019 •
edited
Loading

Link to slides

WIIFY: You will save time for debugging. Other people will appreciate your clean codebase.

Key points:

  • TDD helps you understand requirements better
  • TDD helps you find unexpected behaviors early
  • TDD helps you make a clean codebase
  • Consider complexity and maintenance before applying TDD

CtA: Apply TDD in your next feature if applicable
@Adoby7 Adoby7 self-assigned this Feb 22, 2019
@Xenonym Xenonym added the week 8 label Mar 4, 2019
@Adoby7 Adoby7 added the week 13 label Apr 9, 2019
@Adoby7
Copy link
Contributor Author

Adoby7 commented Apr 15, 2019 •
edited
Loading

new slides
TDD.pptx

WIIFY: You will know how apply TDD correctly in your project, which saves your time for developing in the long term. In addition, other people will appreciate your clean codebase.

Key points:

  • You can follow 3 rules to apply TDD correctly.
  • TDD benefits both you and other developers in the long term.
  • It is better to apply TDD at the beginning.

CtA: Apply TDD in your next project!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Adoby7 Adoby7

Labels
week 8 week 13
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Xenonym @Adoby7