{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Why I Switched to Table Driven Testing approach in Go","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/d51a3879\"></iframe>","width":"100%","height":180,"duration":427,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/why-i-switched-to-table-driven-testing-approach-in-go.\nTable driven tests, also known as parameterized tests, have became very popular over the past few years due to their ability to eliminate repetition.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #go, #table-driven-testing, #code-testing, #code-quality-assurance, #qaing-code, #good-code, #clean-code, #mock-dependencies,  and more.\nThis story was written by: @himanshu.mandhyan. Learn more about this writer by checking @himanshu.mandhyan's about page,\n            and for more stories, please visit hackernoon.com.\nTable driven tests, also known as parameterized tests, have became very popular over the past few years due to their ability to eliminate repetition.","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}