Tips for successful debugging of automation tests

Debugging skills matter

Clean code and best practices

Poor code readability makes it much harder to debug an issue
With clean code, you clearly see an issue after a first look

Extensive reporting

Verbose logging

Clear failure message

assertThat("User is logged in", homePage.hasUserLoggedIn, is(true));
java.lang.AssertionError: User is logged in
Expected: is <true>
but: was <false>

Know your tools

Conclusion

--

--

--

Test Automation Engineer

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Let’s Ditch “Master / Slave” Language from Tech, and Replace it with “Boss / Sub.” Sync Sux.

History of Python

Biweekly Report 1)Make integration tests pass more reliably, some reducer refactoring; 2)Prepare…

Unity-Headers Concept: using server-side hearderbars to create a consistent, customizable and…

OpenLampTech issue #13

I’m Breaking Up With A Simple Life

Laravel 8 Eloquent orWhereHas Condition

Secrets Of Python{Inshorts}

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Andrii Baidachenko

Andrii Baidachenko

Test Automation Engineer

More from Medium

Capturing details and screenshots during a WebdrioverIO test

Assertions in Page Objects

Testing when things are chaotic

Test Automation with TestProject