{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"No Compromises","title":"Are you testing your app or just the framework?","html":"","width":"100%","height":180,"duration":776,"description":"Do you ever finish writing a test and wonder if it is actually proving anything about your code or just confirming that Laravel works?\nIn the latest episode of the No Compromises podcast, we discuss how to tell the difference between tests that validate your logic and tests that merely exercise the framework.\nWe share a practical gut check: if you cannot make a test fail by changing something in your own application code, it probably should not be in your test suite. We also look at this idea from the other direction, asking whether the code being tested is something we actually wrote.\nWe also dig into why testing validation rules is worth the effort even when they feel boilerplate, how feature versus unit test style shapes these decisions, and why the real goal is simply getting to a place where your tests help you ask the right questions.\nJoin the Mastering Laravel community at https://masteringlaravel.io/community\n00:00 Are we testing code or framework\n02:00 Joel metric for framework-only tests\n05:15 Bottom-up testing perspective by test type\n07:36 Why validation rules still deserve tests\n10:40 Silly bit","thumbnail_url":"https://img.transistorcdn.com/Z2EtRaIjEnyUZU7bc944H_cjygcmUk4l_35aeIjws5o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzIzMDM3LzE2Mjc1/MjExMTAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}