In this episode, Vernon and Richard introduce their new podcast and discuss the concept of smoke testing and knowledge work. They explain that smoke testing is a quick test to determine if something is alive or valid, often used when deploying new builds or testing in production. They also discuss the challenges of testing in production and the importance of health checks. In regards to knowledge work, they define it as cognitive work that involves manipulating and processing information based on expertise. They reflect on the recent arguments and discussions on LinkedIn and emphasize the need for nuance and understanding in these conversations.
The conversation explores the challenges and misconceptions surrounding knowledge work in the context of software testing and automation. The speakers discuss how the intellectual effort and expertise involved in testing are often overlooked or undervalued. They highlight the importance of specialised knowledge, innovation, problem-solving, and continuous learning in testing. The conversation also touches on the perception of automated tests and the need to strike a balance between explicit test cases and exploratory testing.
Yes, we are trying to keep this lean, and the above was generated by AI.
00:00 Introducing the Vernon Richard Show
04:47 Exploring the Concept of Smoke Testing
14:32 Understanding Knowledge Work
16:33 Introduction to Knowledge Work
17:11 Defining Knowledge Work
18:03 Characteristics of Knowledge Work
19:22 Perception of Testing as Knowledge Work
24:29 Perception of Programming as Knowledge Work
27:48 Challenges in Communicating Testing Work
31:05 Automated Tests as Test Case 2.0
34:46 Balancing Test Cases and Exploration
35:56 Conclusion and Call for Feedback
Links to stuff we mentioned during the pod:
