Unit Testing
Learn code coverage strategies to improve your unit test design methods and enhance your software's stability and quality.
Software testing fundamentals and systematic test design, from test levels, techniques, and test cases to exploratory testing and reviews.
Learn code coverage strategies to improve your unit test design methods and enhance your software's stability and quality.
Explore Software Testing with AI and discover the synergies, opportunities, and challenges of this innovative technology in software development.
Agile development is transforming software testing methods. Learn about Agile Testing Methods and redefine quality assurance in 2025 projects.
Enhance your code's security with static analysis security testing to detect flaws early and ensure quality software development.
Ensure your migrated system performs equivalent to the legacy system with effective migration testing. Optimize success for software migration testing.
Enhance your software projects with quality requirements engineering and effective software testing to minimize errors.
How does a product test work before the magazine is published? Independent purchasing, blind testing, multiple verifications - including parallels to software testing.
Exploratory testing is not just clicking around randomly. Here is how scoping, timeboxing, and risk focus turn it into a sharp quality tool.
Formal methods sound like an ivory tower, but they provide what testing alone can never do: mathematical proof of correct behavior.
AI-generated test cases in the medical technology environment: how a RAG system remains regulatory clean without tool validation.
600 production runs, one workflow, not a single test for it: How process mining shows what regression testing really needs to cover.
Specialist departments hardly ever test because there is a lack of test knowledge. How an AI assistant called Sherlock is changing this and delivering test cases according to ISO standards.
Two years of exploratory ensemble testing in a real project: What the method brings, where it gets stuck and why testing is suddenly fun.
Performance testing is not the same as load testing, and running capacity tests every sprint is wasting cloud budget on the wrong problem.
Measuring embedded code coverage without instrumentation: Why hardware tracing in system testing solves the observability that unit testing alone can't deliver.
Testing is both art and science. Da Vinci used curiosity, imperfection, and simplicity as tools. So can testers who want real impact.
From unit tests to exploratory testing: which Java tools really count, how Maven controls the test procedure and why sustainability is often underestimated in testing.
Model-based testing kills two birds with one stone: better requirements and ready-made test cases from one workshop.
Testers keep losing the value argument not because their work is wrong, but because they pitch defects instead of business outcomes.
How do you create a board game that delivers real test cases? A team built it - and learned more about testing than expected.
Living quality as an attitude, not just writing test cases: Why it makes the difference and what 150 podcast episodes teach about it.
A bug that only appears after 17 exact steps sounds untestable. Property-based testing finds it anyway, by generating cases humans would never think to write.
Static analysis throws up thousands of findings - AI fixes two thirds of them reliably. What this means for old code bases and where the method clearly reaches its limits.
Fuzzing sounds like chaos, but it's a method: How random input systematically reveals security vulnerabilities and why targeted test data is more useful than pure chance.
Most testers know test design techniques but rarely use them. Four groups, five techniques, and the right selection logic change that.
If you calculate target values for 2,500 signals manually, you lose the connection. How a reference implementation as a test oracle solves this.
From a sluggish monolith with hours of end-to-end testing to fast microservices: Which test strategy really works for this.
280 UI tests, under three minutes, no backend required: How isolated UI testing with mocked API responses becomes faster and more stable than classic component or E2E testing.
Many people know test design methods, but hardly anyone uses them. Why this is the case and how AI closes this gap without making you stop thinking.
Mutation testing is over 50 years old, but hardly anyone uses it. How mutants help to find test gaps and write better code.
25 to 30 test design techniques exist, but most testers hardly use any of them. Why five of them are enough for 90% of all testing tasks.
700.000 lines of code in a combi steamer, 2,000 test cases per night: how test automation really works in device development.
Model-based testing sounds good, but often fails due to a gap between the abstract model and the actual test. Why this is the case and how a two-phase approach can help.
Testing proves bugs, but never freedom from bugs. Formal methods can do this, from type systems to verified kernels, and the effort is more scalable than expected.
Production data often only covers 70% of test cases. How to systematically test data processes and get business and IT on the same page.
90% of failed tests are real bugs, not automation errors. Why no project can do without manual testing.
LLMs testing like a pro: Acceptance Test Driven Development meets fine-tuning - creating a measurable quality process for AI systems.
Lots of unit tests, high test coverage, but still bugs. Why the test pyramid is often used incorrectly and when other approaches make more sense.
Anyone who plans acceptance testing shortly before delivery is testing quality at the most expensive time. What early integration really brings.
Those who accept software usually only test functions. Whether up to 12,000 undiscovered bugs are normal and what "state of the art" really means in legal terms.
Using ChatGPT for test cases, test data and exploratory ideas: What really works, where caution is advised and why prompting matters.
Millions of test cases generated automatically instead of laboriously written by hand: What property-based testing is and what its limitations are.
Automotive testing: a windshield wiper is already considered a safety-critical system. What this means for test methods, standards and everyday life as a tester.
Model-based testing is considered complex and formal. Boxes, arrows and a flowchart are enough to uncover requirement gaps early on and generate test cases.
Finding 80% of errors in 1% of the time: How test impact analysis and test gap analysis are fundamentally changing testing.
Why are hundreds of unit testers created, but the software still doesn't run? Because isolated tests alone do not prove a feature - and that is the problem.
Manual testing is no fun, risk analyses end up in a drawer. Gamification in testing can solve both - with concrete formats such as Bingo-Bongo or Maturity Poker.
How do you test an app that drivers use while driving without distracting them? Test drives, surveys and slow rollouts on 20% of the fleet.
If you only check quality during testing, you've already lost. How unit tests, IDE plugins and contract testers make errors visible earlier.
Cypress instead of Selenium: Why real browser testing is more stable, how component testing saves the test pyramid and where the tool's limits lie.
From carpenter to agile engineering coach: How a career change and a book about system testing sparked an entire career in testing.
6.5 hours of test runtime, reduced to 10-15 minutes: How test case selection across C++ and Java makes it possible.
500.000 players, a 25-year-old game, weekly patches: how game testing really works and why exploratory testing is indispensable.
Reviews are considered cumbersome, but they are not. Which types really help, which pitfalls slow teams down and how a first review succeeds.
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.