Blog Posts

TLDR; As a simple rule, “I might not automate, if I have to create”. But I have done the opposite. I have automated when others would not. And I have waded in when others would have automated. To answer we need to question our situation and build a deeper model of our actual aims, options and capabilities.

TLDR; The instructions on apache and sonatype site are pretty good to help get library released to maven central. But you’ll need to learn about pgp signing and might need more rigour in your pom file. A fairly painless learning process that I recommend you go through and release something to the world.

TLDR; Don’t rule out headless browsers like HTMLUnit, just because no-one uses them in the real world. They might make automating your task easier and faster.

TLDR; using Marp and Pandoc I can write a report and presentation using Markdown, then add other tools to make it ‘pretty’.

TLDR; Even simple changes can use step by step risk based development to allow multiple releases, and will require multiple levels of testing.

I’ve slowly been improving my JavaScript skills. But in a slightly unconventional way…

TLDR; View the IntelliJ log Help -> ‘Show Log in Explorer’

TLDR; With Chrome Code Snippets we can ‘run’ small chunks of code without using the console. And using a gist we can import and export them to a file.

TLDR; learn how to use the dev console and basic JavaScript commands (for, do…while, if…then, variables) to automate under the GUI and augment your interactive technical web testing.

TLDR; Look at what your GUI does. Automate that. And you’ve implemented “APP as API”