Join the presentation on: Testing AI-Based Systems: Considerations for Quality and Risk!
This presentation discusses the specific requirements for testing AI-based systems through the lens of test maturity. It discusses the limitations of conventional test techniques and coverage models when applied to AI components and highlights the need for revised testing strategies.
Register Today: https://zurl.co/IcaJW
🤖 How do you actually know if your AI agent is any good? Great practical read on evaluating AI agent performance metrics, methods & the traps to avoid. A must for anyone moving into LLM evals.
Holistic quality means everyone contributes.
Learn practical ways to:
• Reduce defects
• Improve collaboration
• Build shared ownership
• Strengthen delivery pipelines
Don't miss Sarah Little at Nebraska.Code()!
🔍 "Self-healing" in test automation sounds great on paper but does it actually hold up? Some honest thoughts on the trade-offs worth reading before you commit to it.
From what I’ve seen over the years, tests that exercise a system through the graphical user interface are disproportionally likely to fail for reasons other than an actual, genuine product failure. Call them false positives, call them flaky tests, call them whatever you want.
Stop chasing 100% coverage, start asking "what could go wrong and how badly?"
Great short read on shifting from a coverage mindset to a risk mindset in testing. A reframe every QA engineer and manager should make.
🦆 https://shorturl.at/58toQ
I'm looking for problems by watching our CI server build jobs and telling the devs if a build breaks. (Don't asks about the broken e-mail notification)
I don't call it #QualityEngineering or similar. Just plain / upland #Testing .
#RapidSoftwareTesting goes beyond the execution of predefined scripts and also doesn't reinvent the wheel.
Good, deep testing is doable.
#quality #softwaredevelopment #softwaretesting #agile #kanban #scrum
Escrevi sobre property-based testing com Hypothesis e como essa abordagem ajuda a encontrar casos de borda de forma mais inteligente do que testes baseados só em exemplos.
https://www.riverfount.dev.br/posts/hypothesis_property_based_testing/
A suite de testes está verde. Fixtures bem organizadas, parametrize cobrindo os casos óbvios, mocks isolando as dependências externas. Cobertura em 94%. O PR passa no CI e vai para produção. Três dias depois, um usuário reporta um comportamento estranho. Você reproduz o bug localmente com um input que nunca ocorreu a ninguém testar: uma string vazia em que se esperava pelo menos um caractere, um número negativo em que a função assumia valores positivos, uma lista com um único elemento no qual a lógica de comparação silenciosamente quebra. O teste que teria pego isso seria trivial de escrever — se alguém tivesse pensado em escrever.
Testing AI systems? The old rules no longer apply.
Non-deterministic systems cannot be assessed using deterministic methods. “Pass/Fail” is too narrow.
At #SwissTestingDay, Mike Mannion reflected on key themes:
➡️ probabilities over binary results
➡️ system behaviour over isolated outputs
➡️ testing as a strategic discipline
He also points to approaches like #PUnit for evaluating such systems.
Conference insights: https://dev.karakun.com/2026/04/02/Swiss-Testing-Day.html
Quality Engineering vs Quality Assurance — do you know the difference?
Discover how both approaches impact your software quality, speed, and performance.
Upgrade your testing strategy with expert insights from QA Testing Canada.
Read now: https://www.qatesting.ca/blog/quality-engineering-vs-quality-assurance/
#QualityEngineering #QualityAssurance #SoftwareTesting #QATesting #AutomationTesting #DevOps #SoftwareQuality
WebExpo Conference
imbus Canada Corporation
Aurélien Lair
Nebraska.Code
Sebastian Stautz
Riverfount 
Karakun
qatesting