SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Projects fail because they don’t test. Some fail because they test the wrong things. Others fail because they test too much. In this session, an enterprise consultant turned startup entrepreneur will share project case studies in testing atrocities and what can be learned from them. You’ll come away questioning your own testing. Check your dogma and let’s build better software.
Check out TrackJS JavaScript Error Monitoring
https://trackjs.com/javascript?utm_source=slides&utm_medium=slideshare&utm_term=testing
Projects fail because they don’t test. Some fail because they test the wrong things. Others fail because they test too much. In this session, an enterprise consultant turned startup entrepreneur will share project case studies in testing atrocities and what can be learned from them. You’ll come away questioning your own testing. Check your dogma and let’s build better software.
Check out TrackJS JavaScript Error Monitoring
https://trackjs.com/javascript?utm_source=slides&utm_medium=slideshare&utm_term=testing
15.
They all had their rules…
1. Thou shall test everything
2. Thou shalt not ship code
3. Thou shall have more sys
4. Thou shall abstract test f
5. Thou shalt not duplicate
26.
code coverage %
1000
what do we learn?
not testing
27.
code coverage %
1000
what do we learn?
metrics-driven
incentives
28.
code coverage %
1000
what do we learn?
nothing at all
29.
Testing the Mocks
public void Test_MyObj_With_Mocks() {
Mock<MyObj> mockObj1 = new Mock<MyObj>();
Mock<OtherObj> mockObj2 = new Mock<OtherObj>();
MyObj obj = new MyObj(mockObj1, mockObj2);
mockObj2.expect().toBeCalledWith(mockObj1).andReturn(mockObj1);
obj.method();
mockObj1.assertExpectations();
mockObj2.assertExpectations();
// What are we testing again?
}