Software Testing and Development Blog Posts

I looked at my mobile testing options and I realised that I didn’t have a full toolbox to help me. Particularly in terms of screen recording.

I seem to default to WinMerge for my file and directory comparisons.

When you run your tests in IntelliJ you may have seen an output where only the failing tests are shown in the run pane tree.

If you see the “Maven projects need to be imported” popup in IntelliJ, then do click “Enable Auto-Import”.

I just added a chapter on Date and Time to the “Java For Testers” book.

I have some ‘rules’ that I apply when I take notes as I perform exploratory testing.

When I look back over how I took notes in the past I can see that I tried different experiments with my approach when building those ‘rules’.

I recommend some of my experiments to you now:

“Why are my Junit 4 asserts deprecated?”

This particular case study demonstrates how I think about testing and incorporate automation into my test approach.

We use Maven in the Java For Testers book.

Once you have Maven running it tends to work fine. You mainly experience problems when you initially install it, at the point when you know how to nothing with Maven.

I don’t really like keyword driven frameworks. For a whole bunch of reasons that I won’t go into now, since you came here to learn how to write them.

Well, here’s the secret…

This is old tech. Older than old.