I was lucky enough to participate in the Association for Software Testing ’ s annual conference,CAST2018, the week of August 6. Ashley Hunsberger and I facilitated an all-day tutorial on thewith a highly engaged, originative, international group of 28 testers and developers.

The best piece of any conference is learning, and being inspired with new thought and perspectives. I ’ d like to parcel some of the insights I gained from the splendid workshop and talks I attended.

Seeing patterns that aren ’ t there

Liz Keoghalways trigger new perspective for me. In her opening tonic, “Cynefinfor Testers ”, she talked about how we can deal with uncertainty and peril. One way we, as man, try to deal with an uncertain world is by seeing practice where they don ’ t exist. There are so manycognitive biaseswhich may have helped us in more primitive conditions, but often don ’ t serve us well now.

As we develop new software feature, we often startle to finale that we “ cognize ” how a new features should behave. We run with it, we pen code and automate tests, we proudly show it to our customer - only to learn that we create incorrect assumptions and now we have to do re-work.

Building shared understanding

How do we overcome these biases? It sounds simple - though we know “ unproblematic ” doesn ’ t always mean “ easy ”! Liz commend having conversations. She noted that testers have excellentdeliberate discoveryskills. When examiner, developers, product folks and others get together and talk about a lineament, we can hear just how complex a proposed new feature might be, and act accordingly. In Liz ’ s scale, complexity can range from “ We all know how to do this ” - so obvious you say “ Like this, duh ” - to “ Nobody has done it before ” - a differentiator, like the rattling first camera in a mobile phone.

We can ’ t really “ examination ” a extremely complex new characteristic, but we can useexploration by exampleto learn about it. We can use examples and user scenarios to reduce the complexity, we can have the crucial conversations that build shared understanding of how the feature should comport, what value it can give customers. Behavior-driven development (BDD) is one practice that helps us do that. We turn examples into executable tests at the unit and API/service level, automate them, and use them to lead writing the code that get those tests legislate. Now, we can present even a truly innovative new feature with a minimum of rework. The resulting automated test suite provide living corroboration of how the system behaves as well as protection against regression failures.

When to await for more certainty

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Liz recommends waiting until user interface (UI) uncertainty settles down before trying to automate UI tests. Again, we want to minimize re-work. Keep having conversation until you understand the feature and its value good. In my experience, manoeuver UI development by testing lo-fi mockups and epitome is effective in getting to the last blueprint with less superfluous exertion.

I ’ ve found Mike Cohn ’ sTest Automation Pyramidmodel helpful in most contexts. Pushing test mechanization to the lower tier, where tests run faster, are cheaper to maintain and generally more reliable than UI level tests, has worked good for my teams. But I suppose for most web-based apps, we do demand some UI stage automatise regression examine. Lots of fixation failures can simply be caught when travel through all the bed of the covering.

I ’ ve work on teams who successfully did BDD at the UI level. After listening to LIz ’ s keynote, I ’ m considering the mind to manage uncertainty by diligently automating as many scenarios as possible below the UI, then wait until the UI design is full formed before automatize those UI regression checks. I want to experiment with that, I expect in the long run it could save clip and frustration.

(While we ’ re on the subject of cutting down the time spent on UI examination mechanisation, it ’ s exciting to see thepotentiality of applying technologies like machine learningto make tests way faster, more rich and reliable. We can take advantage of the cloud.)

By automating all these regression examinationemploy leading practices and tools for worthful,low-maintenance exam, testers ’ time is dislodge up so they can add value that create a deviation - by bringing their unequalled perspectives to those former product and feature conversations. Testers see patterns others don ’ t see, we ask enquiry others don ’ t think to ask. The reward comes when someone says “ Wait - that ’ s not right ” while we ’ re discussing how a feature should work - before we drop time writing code and tests!

Accentuate the positive

Liz urged us to focus on positive messages. Start the ball rolling with small changes. Whatever happens, use the“ Yes, and… ”technique from Improv to keep building on the positive. Tell stories about the feature. Amplify the good stories. Since many of us testers often have to render bad news about the merchandise we ’ re testing, we require to keep this at the front of our judgment.

According to Liz, & nbsp; testers are the vanguard of Devops. Let 's embrace that!Don ’ t ask “ how can we make things predictable ” - that ’ s not how innovation occur. Instead, ask “ How can we cope with the volatility. We can ’ t remove all the precariousness, we can ’ t mitigate every risk, we can ’ t be “ failsafe ”. But we can make it safe to fail when test to deliver a new feature. Every failed experiment helps us figure out where to go next.

I ’ ve talked a lot over the years about changing our mindset from “ bug detection ” to “ bug bar ”. Of class we want to catch glitch in code, but it ’ s still more important to prevent them. We need strong relationships among testers, developers, operations, merchandise, occupation stakeholders, customer support and more to sail uncertainty. If we conduct advantage of testers ’ unique position, we can render worthful new lineament in our uncertain world, confident that we ’ ll delight our customers. 

More to come!

Liz ’ s tonic was but the beginning of my CAST eruditeness journey. I ’ ll share more insights on contend peril, hiring excellent testers, includingneurodiverseace, and more in next posts.