Ash Winter | Comments

Diana's goat is the real GOAT. We will struggle to top that.

Ha ha! Bryan's talks are a bit like a journey into Mordor, plenty of mortal peril. :) Seriously though, I like his style, owns the empowered tester with strong opinions on quality vibe. Bryan goes way beyond being an information provider...

I love this format, a deep exploration of a topic is most welcome, helps me get my thoughts out/in order. So much value stored in everyones contributions, long may it continue.

This can vary a bit depending on technology under test but... * Component testing - restAssured with JUnit as a runner with TestContainers for mocking. * Contract testing - Pact is used widely, not sure what PactFlow is though (its the enterprise platform built on top of pact) * External integration test (with an interface) - Postman or Bruno for exploratory testing, not necessarily at one particular level though. * External integration test (code) - restAssured again, with a JUnit runner

At an old job, I asked that everyone from all roles became Quality Engineers when the idea was floated to change the testers job titles. Developers, Ops, Analysts etc were not keen. The word quality in a job title has serious credibility problems and places too much expectation on the Quality Engineer to change the world. For some reason, we are still relying on someone to embody quality...

The world changes around the team too, sometimes forcing that re-forming stage. Great shout Gary, another dimension to the discussion!