You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-37Lines changed: 0 additions & 37 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -994,43 +994,6 @@ Note how simple the test is because the UI (DOM) layer does not mix with the bus
994
994
995
995
The next step could be to test the business logic implemented in "showPreview()" or "hidePreview()".
996
996
997
-
998
-
999
-
### Review test code first
1000
-
1001
-
When reviewing code, always start by reading the code of the tests. Tests are mini use cases of the code that you can drill into.
1002
-
1003
-
It will help you understand the intent of the developer very quickly (could be just by looking at the names of the tests).
1004
-
1005
-
### Practice code katas, learn with pair programming
1006
-
1007
-
Because experience is the _only_ teacher. Ultimately, greatness comes from practicing; applying the theory over and over again, using feedback to get better every time.
1008
-
1009
-
1010
-
### Best practices
1011
-
1012
-
+ Roy Osherove - "JS Unit Testing Good Practices and Horrible Mistakes": https://www.youtube.com/watch?v=iP0Vl-vU3XM
1013
-
+ Steven Sanderson - "Writing Great Unit Tests: Best and Worst Practices": http://blog.stevensanderson.com/2009/08/24/writing-great-unit-tests-best-and-worst-practises/
+ Enrique Amodeo - "Learning Behavior-driven Development with JavaScript": https://www.packtpub.com/application-development/learning-behavior-driven-development-javascript
0 commit comments