I think preparation was the key factor in making this workshop so productive. I came with a proposal for how to approach the testing and lots of questions. The proposal provided a basis for our discussion, and the questions helped us to gain a better understanding and generate new ideas.(3/3)

(3/3)

We now have a rough plan and a list of actions to help us further refine our test strategy.

The plan is as follows: Finish our strategy and preparations this week, then start testing next week.

It was great fun. The actionable outcome was worth the three hours.

(2/3)

In today's post, I will show you how to look beyond the graphical user interface. By exploring and understanding these aspects of the software, you can make better-informed decisions about your testing. (2/2)

atesterstoolkit.substack.com/p/uncover-th...

Congratulations on reaching this milestone! 🎉

It's really great to see such a successful YouTube channel dedicated to testing.

For whimsical software that’s fine, or if you *want* to see a magic trick.

When dealing with important files on my computer, I want something safe, reliable, concrete, understandable.

These questions look at dependencies, flow, change and testability.

It is an attempt to make the best of the limited knowledge we have at the moment we are planning. (2/2)

open.substack.com/pub/atesters...

And I have used all this to improve myself as a tester and the people around me.

My latest article takes a closer look at this.

open.substack.com/pub/atesters...

What a great tool to help us better understand the situation we are in, what the causes might be, and what approaches might help us improve it.

Thanks for sharing!

The test is easy to implement and maintain, helps you to find missing and obsolete keys, and helps you to keep them in sync.