Ever feel like you’re not getting the respect that you deserve in your job? This episode dives deep into the “Respect Dilemma” in tech, especially focusing on software testing versus programming. We look at why some roles seem to earn more respect, what that means for workplace culture, and how you can change things for yourself and your team. Respect isn’t just about manners or titles - it’s about how the system works and how we show up in our roles.

If you’ve worked in agile projects, you might have heard, "Everyone is a developer." But some roles seem to get more recognition than others. Is this because of how we define our jobs, or is it just baked into the way our workplaces run? This episode is a call to action, urging everyone to look at respect both at a personal, process and craft level.

We’re breaking down the difference between self-respect, respect for others, and respect built into your team’s process. You'll see why just doing your job isn’t enough. You have to own your craft, communicate what you do, and make your contributions visible to earn genuine respect. By the end of this episode, you'll have practical steps to make respect part of your daily work, whether you’re writing code, testing, building products, or managing.

00:00 Respect Dilemma

02:41 Human Level Respect

06:31 Self-Respect First

10:17 Respect Cycle

15:37 Knowledge Sharing

18:53 Respectful Organizations

21:26 Final Thoughts

Alan Richardson simplifies the over complicated world of test strategy. Drawing on years of experience creating test strategies and plans, Alan explains the real difference between strategy, approach, and plan. Explaining that what really matters isn’t following templates or writing elaborate documents, but actually thinking through problems, understanding risks, and communicating those ideas clearly.

Are you trying to figure out how to break into the software testing job market or make your next big move? This episode of the EvilTester Show dives deep into the realities of tech recruitment, job search strategies, and career planning for testers - with recruitment veteran Jack Cole from WEDOTech.uk - Whether you're an experienced Test manager, expert Tester, or just starting out, Jack’s decades of industry experience will give you strategies and tips about what works in today’s competitive job seeking world.

In this packed hour-long conversation, we cover everything from market trends, LinkedIn networking, and the recruitment pipeline, to building a career roadmap and even the AI hype machine. Grab your notebook, settle in, and get ready for real insights you can use – plus a few stories from the trenches and actionable tips for every step of your job hunt.

We keep things down-to-earth and practical – no stuffy jargon, just the honest, practical advice that will help you stand out, get noticed, and map your next steps with confidence.

Welcome to Episode 22 of The Evil Tester Show, where we're diving into the fascinating world of practice with the renowned James Lyndsay. In this conversation, your host Alan Richardson chats with James about the essence of practice in software testing, exploring how exercises and real-world scenarios can enrich our skills. James shares insights on his weekly online practice sessions and the interactive Test Lab concept, offering a dynamic playground for testers.

Discover how practice blends with rehearsal and learning, and delve into the intriguing intersection of testing and development. With firsthand experiences in software experiments, fencing, and scientific investigation, James and Alan discuss the art of modeling and exploring software systems. Whether you're refining your testing techniques or embracing new perspectives with AI, this episode offers a wealth of wisdom for testers at all levels.

Join us as we learn, laugh, and leap into the realm of testing practice. Tune in, engage with new ideas, and maybe even find inspiration for your own practice sessions. Don't forget to check out James's resources at https://workroom-productions.com for more testing challenges and exercises.

In this episode of The Evil Tester Show, host Alan Richardson describes context-driven testing. Is there really such a thing as context-driven testing, or is it just a phrase we use to describe our testing approach? Alan explores the intricacies of context in testing, discussing its evolving nature, the impact of context on testing practices, and the challenges in defining it.

From the origins of the term by James Bach, Brian Marick, Brett Petichord, and Cem Kaner, to Alan’s personal insights on systems within systems and how context impacts our testing methodologies, this episode provides a comprehensive look at how context affects software testing. Alan also critiques the principles of context-driven testing and emphasizes the importance of adapting to projects without being swayed by ideologies.

We explore how to navigate context in testing environments, adapt our approaches, and effectively challenge and evolve systems. Discover the importance of context-driven testing in software development, exploring models, adaptability, and useful practices.

This episode covers the Test Automation Pyramid, created by Mike Cohen in 2008-2009 in the book "Succeeding With Agile". We will go beyond the diagram and look at the model that supports it. Then deep dive into the model to explore it's meaning in relation to Automated Execution Coverage, not Testing.

- The model was created by Mike Cohen in 2008-2009 in the book "Succeeding With Agile."

- The original model focused on UI, service level, and unit level automation.

- Over the years, different interpretations and variations of the model have emerged.

- The term "service level" in the model has led to ambiguity and different interpretations.

- The diagram in the model is a simplified representation of a deeper underlying model.

- The focus should be on achieving coverage at the most appropriate level in the system.

- The model addresses the importance of avoiding duplication and redundancy in automated coverage.

- The process and team structure can impact the effectiveness of the model.

- The model can be reframed as an automated execution coverage pyramid.

The most common Testing Entities that I've encountered over the years are:

• Test Condition
• Test Scenario
• Test Case
• Test Script

In my Testing I pretty much now have:

• Test Idea
• Test Log (Execution Log)

Is there any value in the original Testing Entities? There might be if we view them as logical concepts, but not really as physical artifacts.

Top 3 Phrases that should carry trigger warnings for the Test Community:

- Manual Testing

- Test Automation

- Quality Assurance

In this episode I'm going to talk about Manual Testing.

So that's your Trigger Warning.

And I'm going to talk about what we might want to say instead of "Manual Testing"