Software Testing and Development Blog Posts
Subscribe to the full blog feed using RSS
Subscribe to the full blog feed using RSS
With so many conferences moving online, it seems worthwhile sharing a few tips about online presenting.
And that’s the topic of this podcast.
TLDR; A collection of tips for presenting online presented on The Evil Tester Show Podcast Episode: get a decent microphone.
500+ videos of experience, crammed into one tiny blog post.
TLDR; A lot of good resources for learning JavaScript exist. And you do not need to install an IDE, you can learn JavaScript in the console.
TLDR; Coverage requires some sort of model. We can organise code to support review against a mental model, and some models are executable. Other models we compare against the output of execution.
I was asked a series of questions: How can we document what an automated test does and covers without adding a lot of overhead? How do we know what is not covered by automation?
I receive a lot of emails asking which way should people focus their career - Testing? Programming? Automating?
And that’s what I cover in this podcast.
TLDR; Observation in real time. Interrogation after the act. Bringing Interrogation closer to Observation can help detect issues during a process. The depth of Observation and Interrogation changes depending on our knowledge of the system and technology. And we may not be done, if our observation was limited.
When I test I make a distinction between Observation and Interrogation and I’m going to explain what that means, and show you hands on example of how that distinction helps me improve my testing and the scope of of my testing.
TLDR; Testing uses models to target the system, and our information is constrained by the models we use and build. We can introduce variation to increase the possibility of finding information related to bugs. We have to take care not to develop false confidence.
TLDR; The Art of War Chapter 13, on spies, is directly applicable for interpretation in terms of Software Testing.
TLDR; Getting started with programming is the hardest part. Installing the IDE, adding dependencies, writing your first test. Pick whichever language you have someone to help you with, or you have a tutorial to work through. Switching languages when you know one is not too hard so do not worry about being stuck with a language, focus on getting started.
These comics have been collated here from individual blog posts over the years.