Advertisement
Case Studies in Terrible Testing
Nov. 4, 2015•0 likes•545 views
2 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Download to read offline
Report
Technology
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
Todd GardnerFollow
Software Engineer and Entrepreneur at TrackJS LLCAdvertisement
Case Studies in Terrible Testing
- TERRIBLE TESTING case studies in
- are you testing the right things?
- I have no idea
- PROJECTS SOFTWARE TESTING and what they taught me about 5
- toddhgardner Todd H Gardner !
- 1Big Todd’s Awesome CRM
- 1 Delivera CustomerRelationshipManagement systemto replacead-hoc processesfor internalsalesteams
- I have no idea what I’m doing
- Consulting!
- They have no idea what they’re doing
- 70% Code Coverage REQUIRED
- Assertion-Free Testing public void Test_MyObj_For_Coverage() { MyObj obj = new MyObj(); try { obj.method1(); } catch (Exception e) {} try { obj.method2(); } catch (Exception e) {} try { obj.method3(); } catch (Exception e) {} // 100% Coverage, W00t! }
- Cool Tests Bro
- 1Big Todd’s Awesome CRM The Aftermath
- 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
- goodness testiness coverage test code ratio
- It’s unprofessional to ship untested code “
- 2Big Corp’s Video Academy
- 2 Createa online Video Training Platform for crypto-zoologists
- unit code coverage 100% 1000
- MOCKS
- code analysis metrics
- BUGS!
- 2Big Corp’s Video Academy The Aftermath
- code coverage % 1000 what do we learn?
- code coverage % 1000 what do we learn? not testing
- code coverage % 1000 what do we learn? metrics-driven incentives
- code coverage % 1000 what do we learn? nothing at all
- 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? }
- Unit Tests
- Test-Induced http://david.heinemeierhansson.com/2014/test-induced-design-damage.html Design Damage
- 3Acme’s Collaboration ComputingPlatform
- 3 Developa platformforSpiesto Upload ConfidentialData andCollaborateon missions.
- Market and Technology FRONTIERS
- $2M / Mo Over 200 of the Cleverest Designers, Developers, and Testers Burning
- Advanced TECHNOLOGY
- System Tests Integration Tests Unit Tests Selenium UI and Services Inter-Module Contract Tests TDD, Conversation-based tests Testing Pyramid
- WE BUILT IT
- NO ONE CAME
- 3Acme’s Collaboration ComputingPlatform The Aftermath
- System Tests Integration Tests Unit Tests Testing Pyramid
- System Tests Integration Tests Unit Tests Testing Pyramid Interface Risk Orchestration Risk Functional Risk
- System Tests Integration Tests Unit Tests Testing Pyramid Interface Risk Orchestration Risk Functional Risk User Tests Market Risk
- Interface Risk Orchestration Risk Functional Risk Market Risk Testing Scales
- Interface Risk Orchestration Risk Functional Risk Market Risk Testing Scales System Tests Integration Tests User Tests Unit Tests
- 4Widget eCommerce Monolith’s Sell-a-majig
- 4 Expandthe Widget Ecommerce platformwithmoreproducts
- yet another ECOMMERCE project
- lots of captive USERS
- Interface Risk Orchestration Risk Functional Risk Market Risk Testing Scales
- Interface Orchestration Functional Market Testing Scales System Tests Integration Tests User Tests Unit Tests
- it shipped UGLY
- customers kept BUYING
- Prints Money the dirty old duct-taped machine that tm
- 4Widget eCommerce Monolith’s Sell-a-majig The Aftermath
- Monolith ECommerce Acme Collaboration Information Technology Uninteresting Fragile Technology Poorly Tested Success! Engineering Advancing Latest Technology Well Tested Failure!
- Monolith ECommerce Acme Collaboration Success! Failure! High RiskLow Risk
- SYSTEM Purpose Criticality Lifespan Frequency CONFIDENCE
- 5 My Startup
- 5findandfix JavaScriptbugs in modernweb applications …andbuilda betterweb
- {Track:js} http://trackjs.com JavaScript Error Monitoring
- User Activity AJAX Requests Console Logging Browser Context Inline Source
- Interface Risk Orchestration Risk Functional Risk Market Risk Testing Scales
- My Money! This time it’s
- Launch Fast and measure
- Simple Decoupled Obvious Abstract & &
- Plumbing Services
- Interface Risk Orchestration Risk Functional Risk Market Risk Testing Scales System Tests Integration Tests User Tests Unit Tests
- Service Model Test Fixture Other Services Wrapper Data Unit Test Integration Test Testing Structure
- “beta” Service Dragons be here! Testing Structure Canary Users Analytics Monitoring
- FAST TO FIXis almost as good as NEVER BROKEN (and sometimes better)
- PROJECTS SOFTWARE TESTING and what they taught me about 5
- 1 Big Todd’s Awesome CRM METRICS don’t test to hit
- 2 Big Corp’s Video Academy BREAKING test what is
- 3 Acme’s Collaboration ComputingPlatform SCARIEST test the thing first
- 4 Widget eCommerce Monolith’s Sell-a-majig CUSTOMER USE tests can’tsubstitutefor
- 5 JavaScriptError Tracking TrackJS’s MONITORING can substitutefor tests
- {Track:js} http://trackjs.com JavaScript Error Monitoring
- TERRIBLE TESTING case studies in toddhgardner! " todd@trackjs.com
Advertisement