Skip to main content

Search...

Podcast: Software Testing, AI and Quality Insights : Page 5 of 16

Legacy apps automated
Legacy apps automated

Legacy apps automated

From two weeks of manual testing to three hours: how an AI-based solution automates legacy apps without element IDs.

Tools Don’t Solve Test Automation
Tools Don’t Solve Test Automation

Tools Don’t Solve Test Automation

A gaming company logged nearly 5,000 defects in eight weeks. Better test automation strategy, not better tools, is how you change that picture.

Quality Storming
Quality Storming

Quality Storming

Errors usually occur long before anyone tests. Quality Storming makes visible where quality is lost in the process - before it's too late.

Performance Testing is not Load Testing
Performance Testing is not Load Testing

Performance Testing is not Load Testing

Performance testing is not the same as load testing, and running capacity tests every sprint is wasting cloud budget on the wrong problem.

HUSTEF Recap
HUSTEF Recap

HUSTEF Recap

From 150 attendees to 705 tickets sold, HUSTEF grew by caring about speakers and community over profit. Here's what makes it work.

Man vs. machine: Who judges more fairly?
Man vs. machine: Who judges more fairly?

Man vs. machine: Who judges more fairly?

AI systems have bias, but the real problem is that people adopt it without realizing it. What this means for the use of AI in companies.

About the Visibility of Testers
About the Visibility of Testers

About the Visibility of Testers

Testers rarely lack skill, they lack visibility, and that gap quietly limits careers and team quality. Show, share and shine are the moves.

Legal pitfalls in software contracts
Legal pitfalls in software contracts

Legal pitfalls in software contracts

Two missing sentences in a software contract can drive a company into bankruptcy. Why agile software projects end up as contracts for work.

Control what you can control
Control what you can control

Control what you can control

Stoic philosophy turns out to be a sharper tool for product decisions than most agile frameworks. Here's why outcome focus misleads teams.

Dynamic analysis for embedded systems
Dynamic analysis for embedded systems

Dynamic analysis for embedded systems

Measuring embedded code coverage without instrumentation: Why hardware tracing in system testing solves the observability that unit testing alone can't deliver.

What if Da Vinci had been a software tester?
What if Da Vinci had been a software tester?

What if Da Vinci had been a software tester?

Testing is both art and science. Da Vinci used curiosity, imperfection, and simplicity as tools. So can testers who want real impact.

Practical software testing with Java
Practical software testing with Java

Practical software testing with Java

From unit tests to exploratory testing, only some Java tools really count in practice. How Maven controls the whole test procedure reliably.

One Breath Can Change Your Project
One Breath Can Change Your Project

One Breath Can Change Your Project

Stress and burnout cost the IT industry a fortune, yet one minute of breathing before a meeting can change how a whole team communicates.

Code quality, metrics and mindset for students
Code quality, metrics and mindset for students

Code quality, metrics and mindset for students

Teaching testing in university before real projects put pressure on you: Why architecture trumps testability and ChatGPT disguises it.

Do your tools fit your real needs?
Do your tools fit your real needs?

Do your tools fit your real needs?

Picking the wrong end-to-end test framework can leave whole browsers untested. Here's how to match tools to real project needs before it costs you.

More quality in requirements with AI
More quality in requirements with AI

More quality in requirements with AI

Vague requirements are the most expensive problem in testing. How AI really helps when determining, formulating and checking requirements.

Fail more to learn faster
Fail more to learn faster

Fail more to learn faster

"It depends" is not a dodge. It is the only honest answer when context shapes every testing decision, and here is why that matters.