WAIT #3 Call For Participation
Call for participation in WAIT #3, a peer conference on AI in software testing, seeking experienced testers to share and evaluate real-world AI testing experiences.
Call for participation in WAIT #3, a peer conference on AI in software testing, seeking experienced testers to share and evaluate real-world AI testing experiences.
A consultant discusses three key questions to assess an organization's test automation strategy and ensure it aligns with business goals.
A critical analysis of whether test automation truly reduces stress and disruptions, or if it can initially increase workload and pressure on teams.
Explores how comprehensive testing enables the 'Four Rules of Simple Design,' focusing on how tests support change, intention, and duplication removal.
Discusses the pitfalls of automating tests just to follow trends, emphasizing business value over mimicking tech giants.
A guide on selecting the right teams and projects for successful test automation by prioritizing high-probability wins over maximum theoretical impact.
The article argues that software testing is a valid and valuable entry point into the IT industry, addressing common criticisms of this view.
Argues that test code should prioritize readability and avoid excessive indirection, even at the cost of code duplication, to simplify debugging.
A guide to verifying .NET dependency injection containers to catch missing registrations and captive dependencies at startup.
Explores the concept of testability in software architecture, its importance for quality and continuous delivery, and breaks down key components like controllability.
Explores the importance and benefits of automated testing in software development, addressing common barriers and the value of testing culture.
Explores why data and ML pipeline tests break incorrectly and offers strategies for writing more robust unit, schema, and integration tests.
Explains end-to-end (E2E) testing methodology, its purpose in simulating real user scenarios, and its role in a robust CI practice.
A guide on introducing Test-Driven Development (TDD) to a software team through leading by example and building consensus.
A developer investigates a bug in a Space War game where duplicate bases cause crashes, detailing the debugging process and unit testing.
A discussion on analyzing confusing Gherkin scenarios in software testing, focusing on understanding domain intent before rewriting.
Learn how to write automated tests for your Django project to verify functionality and save time on manual checks.
A guide to diagnosing and fixing slow CI/CD pipelines, focusing on reducing lead time to under 15 minutes with anti-patterns and optimization strategies.
A software developer draws parallels between scientific experiments and software development, discussing how unexpected test results and failures can be valuable learning opportunities.
Explores using resilient randomized tests to improve software system robustness and prevent regressions during maintenance and change.