Software Testing and Development Blog Posts
Subscribe to the full blog feed using RSS
Subscribe to the full blog feed using RSS
TLDR; The Tester in me was not satisfied by the TDD of FizzBuzz so I expanded the coverage with some simple acceptance testing modeled by automated @Test methods.
Previously on “Testers TDD” I created a version of FizzBuzz using TDD we now move on to the Acceptance Testing of FizzBuzz, but do we need to?
UKStar is in march I helped organise it as part of the programme committee But I’m also doing a workshop with Gustav Khun which we have been planning.
I’m not sure I’ve looked forward to a workshop quite as much as this one.
Gustav is a Cognitive Psychologist and practicing Magician (he’s been on TV!) and we are going to explain some of the psychological principles of magic and I’ll map them on to Software Testing. Why? Because my MORIM model was built during the time that I talked my way into the Magic Circle in London for a year and I learned to study Magic and apply what I learned directly to testing. This is something I’ve wanted to cover for years but felt I lacked the credibility for the ‘Magic’ part. So I teamed up with Gustav to make sure we have a solid basis in Magic, Cognitive Psychology and Software Testing.
TLDR; Four JUnit @Test methods to create a FizzBuzz solution using Test Driven Development (TDD) with Java Junit.
TLDR; Do you practice your testing? One way involves picking a random game and exploiting it.
TLDR; I can view Problem Solving as Problem Identification, Problem Solution Construction, Solution Evaluation and I can map that on to Software Development to help me communicate in normal language.
TLDR; A career in Software Testing is not an ’easy’ ride, if you are not careful then you can get stuck. But if you work at it then you can make a difference to your company and the community at large.
I present a keynote at the internal Rabobank testing conference in Utrecht. Covering: Agility, Agile, Cybernetics, Integration testing, Technical Testing, Automating, and more…
Synopsis:
My aim here is to tell you that I learned to work with Agility rather than work with the Agile Rituals and Definitions. And I learned to trust that working with Agility trumps Rituals and Definitions the hard way. Because sticking to rituals and definitions led to rigidity, rather than agility.
Presented as a UKStar 2018 webinar. I show how to void the use of Flaky to describe intermittent failure for your automated execution. Common causes of intermittent execution and some solutions.
TLDR; Testability is for humans. Automatability (Automatizability) is for applications.
Do you make New Year Resolutions? I set goals that I believe in, then create work plans, and adjust my expectations based on what I do, and I do change my mind based on experience. But I also, use my testing skills to do all of that.