Automatic test case selection for regression testing
6.5 hours of test runtime, reduced to 10-15 minutes: How test case selection across C++ and Java makes it possible.
6.5 hours of test runtime, reduced to 10-15 minutes: How test case selection across C++ and Java makes it possible.
Sustainability in software projects does not start with deployment, but with the requirements. How this works in concrete terms and where to get the most out of the test process.
500.000 players, a 25-year-old game, weekly patches: how game testing really works and why exploratory testing is indispensable.
Addressing mental health at work, but how? Those who take the first step often get others on board - and change the team culture more than any ritual.
Contract-based testing decouples providers and consumers so that interface changes no longer deliver any nasty surprises. How this works in practice.
68 countries, over 800,000 certificates, almost all voluntary: what's really behind the ISTQB and where the new CTFL 4.0 is heading.
Selenium is not a test tool, but a browser automation. Why this difference determines how you integrate test automation into your team.
Reviews are considered cumbersome, but they are not. Which types really help, which pitfalls slow teams down and how a first review succeeds.
200 failed tests, but only seven real causes: How machine learning radically simplifies testing operations without rationalizing away roles.
Why do developers and business departments read the same requirement and still understand something different? BDD and Given-When-Then close precisely this gap.
Quality in agile projects is not created at the back in acceptance testing, but at the very front in dialog. Why this is the case and what often goes wrong.
Quality is not a task for the testing department, but an attitude throughout the entire team. Three factors make the difference.