{
  "$type": "site.standard.document",
  "description": "They say if it's not broken, don't fix it. So why are we running tests on tests on tests that aren't business-critical? There's an art to testing beyond just striving to get 100% coverage. In fact, over-testing can actually hamper your progress more than help it. Meanwhile, Chuck's wondering why it'",
  "path": "/mystery-makers-monday-testing-and-graphql",
  "publishedAt": "2022-06-02T07:00:00.000Z",
  "site": "at://did:plc:3xtte5zonglhdotitdwmukhq/site.standard.publication/3mnwyowjjysmi",
  "tags": [
    "podcast"
  ],
  "textContent": "They say if it's not broken, don't fix it. So why are we running tests on tests on tests that aren't business-critical? There's an art to testing beyond just striving to get 100% coverage. In fact, over-testing can actually hamper your progress more than help it. Meanwhile, Chuck's wondering why it's not possible to have a union of enums in GraphQL.\n\nIn this episode, Chuck and Robbie discuss some tech frustrations, lessons for the React community, why Ship Shape implemented spam traps, and a whatnot on all things alcohol, sports, Friends, and Robbie's (seemingly endless) truck saga. \n\nKey Takeaways\n\n * [01:50] - A lengthy whiskey review. \n * [22:53] - Why getting carried away with tests becomes your downfall. \n * [34:50] - Why Chuck thinks these tests in the React community are useless. \n * [38:16] - Chuck's GraphQL confusion. \n * [40:49] - A browser bug Chuck noticed. \n * [44:09] - Robbie's non-sponsored plug.\n * [44:50] - A sports-themed whatnot and an update on Robbie's truck saga. \n\nQuotes\n\n[26:52] - \"There are things that warrant tests and things that don't and there are good best practices for writing them.\" ~ @rwwagner90 [https://twitter.com/rwwagner90]\n\n[33:44] - \"Sometimes people will just chase the goal of as close to 100% coverage as possible and then you end up with a bunch of egregious tests along the way.\" ~ @CharlesWthe3rd [https://twitter.com/CharlesWthe3rd]\n\n[34:00] - \"You need to test what's business-critical. You can do the other tests if you have the time. But there were a lot of tests that really didn't even check anything. And it's kind of arbitrary — you got that coverage, but you weren't doing anything.\" ~ @rwwagner90 [https://twitter.com/rwwagner90]\n\n[36:32] - \"Cypress is a great example of having integration testing in context where you can get visual progression testing too so [you] have some understanding there.\" ~ @CharlesWthe3rd [https://twitter.com/CharlesWthe3rd]\n\nLinks\n\n * Maker's Mark No. 46 [https://www.makersmark.com/makers-mark-46]\n * Maker's Mark Cask Strength [https://www.makersmark.com/makers-mark-cask-strength]\n * Maker's Mark Private Selection [https://www.makersmark.com/makers-mark-private-selection]\n * Woodford Reserve [https://www.woodfordreserve.com/]\n * Jack Rose Dining Saloon [http://jackrosediningsaloon.com/]\n * The FRIENDS Experience  [https://www.friendstheexperience.com/]\n * Mocha [https://mochajs.org/]\n * Jest [https://jestjs.io/]\n * Ember.js [https://emberjs.com/]\n * Slack [http://slack.com]\n * reCAPTCHA [https://www.google.com/recaptcha/about/]\n * React [https://reactjs.org/]\n * Cypress  [https://www.cypress.io/]\n * Facebook [http://facebook.com]\n * Vite [https://vitejs.dev/] \n * GraphQL [https://graphql.org/]\n * Chuck on Twitter [https://twitter.com/CharlesWthe3rd]\n * Elon Musk [https://twitter.com/elonmusk]\n * Starlink [https://www.starlink.com/]\n * Netlify  [https://www.netlify.com/]\n * Middesk [https://www.middesk.com/agent]\n * QuickBooks [https://quickbooks.intuit.com/]\n * Walkabout Mini Golf on Oculus Quest [https://www.oculus.com/experiences/quest/2462678267173943/]\n * Holey Moley [https://abc.com/shows/holey-moley]\n * Steph Curry [https://twitter.com/StephenCurry30] \n * Topgolf [https://topgolf.com/us/]\n * Rivian [https://rivian.com/]",
  "title": "Mystery Maker's Monday, Testing, and GraphQL"
}