Software Testing and Development Blog Posts

TLDR; JavascriptExecutor requires us to learn JavaScript and use the Browser Console, and check your locator assumptions using FirePath

TLDR; split code across lines and breakpoint, and use browser dev tools to test the locators used.

TLDR; right click on a breakpoint and add code that returns a boolean to make it a conditional breakpoint

TLDR; Q: what is the best Page Object framework? A: I don’t know. I don’t use any

TLDR; We can use JUnit to execute code to support any type of testing.

Is it REST? Does it matter? We have to test it anyway.

TLDR: fixes are important. when we have work to do, sometimes a workaround is more important

Here’s the situation. You’ve written some code to automatically execute your application. You’re using Selenium WebDriver. Bam. Something goes wrong. You don’t know what to do. Here are some tips.

I have deliberately created a failing test. Obviously deliberately since I would never ever create such simple issues in code.

TLDR; Condemn? No. Support? I do like parts of the paper. Censor? No.

And now I’m doing something I don’t like: writing a blog post in response to ‘something on the internet’. I’m writing a blog post which I don’t think has any practical value. I warn you now. I don’t think you will find much humour herein either. I have added a comedy punchline at the bottom though, if you want to skip ahead.