{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Code Smell 312 - You Put Multiple Assertions in One Test, Making Failures Hard to Analyze","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/589fae62\"></iframe>","width":"100%","height":180,"duration":380,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/code-smell-312-you-put-multiple-assertions-in-one-test-making-failures-hard-to-analyze.\nYou put multiple assertions in one test, making failures hard to analyze.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #programming, #software-development, #code-smells, #common-code-smells, #refactoring, #refactor-legacy-code, #code-smell-312, #hackernoon-top-story,  and more.\nThis story was written by: @mcsee. Learn more about this writer by checking @mcsee's about page,\n            and for more stories, please visit hackernoon.com.\nYou put multiple assertions in one test, making failures hard to analyze.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}