How to write less code in tests
<p>One year ago we started trying <a href="https://maestro.mobile.dev/" rel="noopener ugc nofollow" target="_blank">Maestro</a>. It’s a game changer for the UI tests!</p>
<p>As our UI tests were a mess, we got encouraged to try it. The results for the first use case were impressive: <strong>we reduced from more than 260 lines to just 21,</strong> <strong>almost 92% less!</strong></p>
<blockquote>
<p>It’s well known that the fewer lines of code, the fewer the errors.</p>
</blockquote>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/0*F2W5fhkxsG5lnKkH" style="height:1050px; width:700px" /></p>
<p>Photo by <a href="https://unsplash.com/@ahmad_elsafty?utm_source=medium&utm_medium=referral" rel="noopener ugc nofollow" target="_blank">ahmad elsafty</a> on <a href="https://unsplash.com/?utm_source=medium&utm_medium=referral" rel="noopener ugc nofollow" target="_blank">Unsplash</a></p>
<p>To add more context to the article, I will focus on this use case: Our drivers have to input the center, their driver ID, the route and the expedition lane, and also the plate of the vehicle to log in to our Delivery App.</p>
<p><a href="https://medium.com/mercadona-tech/how-to-write-less-code-in-tests-a5f8d556194e"><strong>Read More</strong></a></p>