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
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -705,6 +705,12 @@ Articles:
705
705
* Tests lock in behaviour
706
706
* Tests give you confidence to change someone else’s code
707
707
*[Testing Strategies in a Microservices Architecture](http://martinfowler.com/articles/microservice-testing/) (Martin Fowler) is an awesome resources explaining how to test a service properly.
* Be clear about the different types of tests that you want to write. Agree on the naming in your team and find consensus on the scope of each type of test.
712
+
* Every single test in your test suite is additional baggage and doesn't come for free.
713
+
* Test code is as important as production code.
708
714
*[A Quick Puzzle to Test Your Problem Solving](http://www.nytimes.com/interactive/2015/07/03/upshot/a-quick-puzzle-to-test-your-problem-solving.html?_r=0)... and a great way to learn about confirmation bias and why you're mostly writing positive test cases.
709
715
*[The test pyramid](http://martinfowler.com/bliki/TestPyramid.html)
710
716
*[Just Say No to More End-to-End Tests](https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html)
0 commit comments