Activity

From manual to automated: a tester’s journey into AI

Nice one for doing the Call for Insights and supporting Jonathan.

From manual to automated: a tester’s journey into AI

From manual to automated: a tester’s journey into AI

From manual to automated: a tester’s journey into AI

From manual to automated: a tester’s journey into AI

Master the RICCE framework to transition from manual testing to AI-augmented automation by leveraging structured prompting and the Playwright MCP agent ecosystem.

Thanks for doing a Call for Insights!

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Why software testers should write documentation even if no one else reads it

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Creating a resilient test framework with the Playwright Page Object Model (POM)

Implement the Playwright Page Object Model (POM) to build maintainable, resilient test suites by centralizing page interactions and separating them from test logic.

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

This Week in Quality

This Week in Quality

Share your week’s highlights, challenges, and lessons in quality

Why software testers should write documentation even if no one else reads it

Anti-Pattern

Definitions of Anti-Pattern

Why software testers should write documentation even if no one else reads it

I am greatly enjoying watch you test! It's like, yes, this IS my job, I am doing it right

I am greatly enjoying watch you test! It's like, yes, this IS my job, I am doing it right

Don’t automate everything, review everything

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

OpenAI Will Shut Down Sora Video App; Disney Drops Plans for $1 Billion Investment

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

"Addendum to this article - "The Sticky Tentacles of AI" https://www.ministryoftesting.com/moments/the-sticky-tentacles-of-ai A short Moment reflecting on the use of AI to integrate documentation where AI can proactively identify gaps in the documenta..."

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it

Why software testers should write documentation even if no one else reads it