{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"No Compromises","title":"Why do you write your tests like that?","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/6c2199b9\"></iframe>","width":"100%","height":180,"duration":880,"description":"We discuss two \"interesting\" patterns we've observed in a number of Laravel projects. Let's take a step back and think about why we write tests the way we do.1:06 - One weird pattern we’ve seen in Laravel project tests2:23 - Can you explain why you’re doing this?3:50 - “It’s more readable”5:55 - Principle: learn a thing, do a thing, dissect a thing6:30 - Is it okay to have code duplication in tests?8:20 - How tests are different from application code11:16 - Don’t add application code just for your tests13:06 - Silly bitNeed help building a test suite for your Laravel app or making your existing tests more reliable? Click the link and book a free call to see how we can help.","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}