Blog Posts

TLDR; Automating is not limited to “Test Automation”. With the ability to code, we gain the flexibility to approach problems in multiple ways. We can refactor tactical code to become strategic code.

I needed to migrate some data from one system to another. To do it manually would have taken me about 1.5 to 2 days. I automated tactically and was done in 2 hours.

TLDR; Any time you see a list of pros and cons on the internet and ‘believe’ the pro or con, ask yourself “But What if…?”

I see a lot of pro and con posts and questions on the internet. They lack the context behind the pro and con identification, so I find it hard to use them directly.

This is a test report on the testing I performed after migrating my blogs on 28th December 2018, from 14:00 - 18:26.

Selenium IDE has been getting some press recently since AppliTools are resurrecting it.

TLDR; Coding Tips for beginners.Write your code as temporary comments, remove syntax errors as soon as you see them.

Here are a few tips I’ve been verbally passing on when teaching people on my Java For Testers face to face training.

A great way to start introducing automated execution and tooling into your test process is to conduct a proof of concept (POC).

A POC can often provide, in a few days, far more information than an extended RFP and trial evaluation process, assuming the right people are involved and the aims are clear.

EvilTester.com is a static site built using HuGo

I’ve been meaning to migrate it to https, but haven’t found the time recently.

Today I found the time.

Black Friday means cheap deals.

Testing is already the ‘cheap’ and undervalued relation in Software Development. Testers are paid less than programmers. Testing is outsourced more often and programming because it is seen as less valuable. Testing is viewed as more of a junior role than programming.

Every day is Black Friday for Software Testing.

I presented:

• a keynote “Exploring Testing from First Principles”. Where I treat testing as something we can build a model of by asking common sense questions, and see how far this approach takes us in developing thought processes around technical and technical knowledge.
• the full day version of my “Testability workshop” looking at the different attributes, skills and thought processes around Testability.
• a “Lightning Strikes the Keynotes”.

Logistics

• November 12th - 15th, 2018
• Eurostar Conference

The Keynote Blurb

What if we knew nothing about testing, how would we start? Does our every day life provides the tools we need to help us investigate a domain and develop the necessary skills we need to survive? This talk will start by assuming that about Software Testing and Technical software testing we know nothing. And then, using a process of questioning and exploration we will see how far we get in terms of building a model of Software Testing and Testing an application from a Technical perspective.

TLDR; Rather than migration your assertions line by line, create an abstraction class to represent the new implementation and then perform inline refactoring.

I’m experimenting with migrating my projects to JUnit 5.

Many of the “how to migrate to JUnit 5” blog posts show differences, but not a lot of strategies. I used a Branch By Abstraction strategy to migrate JUnit 4 Assertions. This allowed me to experiment with using JUnit5 assertions or AssertJ assertions.