
Requirements Engineering: Every Test Case Design Is a Review
Requirements engineering decides how good testing can be. Test case design exposes gaps, and traceability shows which tests a change affects.
Thoughts and insights on software testing, quality assurance, and the future of technology.

Requirements engineering decides how good testing can be. Test case design exposes gaps, and traceability shows which tests a change affects.

Software developer responsibility grows as code shapes safety, fairness and daily life. Whoever designs the modern world has to weigh what they build.

Stoicism helps with decision making in the AI era: machines do more of the work, we decide more often. Control, virtue and acceptance bring clarity.

Integrating Agile software testing ensures quality from the start. Transform your testing mindset with DevOps and automated processes.

Focus on people: when AI writes much of the code, decisions on quality, ethics and vision land with humans. Companies should invest in them as in tools.

Additive bias makes teams add features, code and test cases rather than remove any. Complexity and debt grow, and subtraction is the overlooked fix.

Good software supports its users, and matching the spec is only part of that. A camper van shows how software lets people down and which questions help.

The democratization of software development is near: AI code generators and no-code platforms let anyone build apps. That also calls for responsibility.

Test data problems won't vanish with AI. First ask which data you really need, delete the rest and build a data architecture that works across systems.

For, against or both: people and teams find it easier to unite against something. Winning over the naysayers takes a goal that appeals emotionally.

AI in software testing helps with test cases, test data and error analysis. Testing AI systems means rethinking quality criteria such as data quality.

Process models rarely run in pure form: most teams mix Scrum, PRINCE2 and the V-model. Processes refined in retrospectives leave room for creativity.

SAP testing starts with business processes and risk. PRACTICES UP covers eleven focus areas, and five data classes structure the test data.

Detox at work starts small: quiet moments during the day and a sprint break in which the team does nothing at all help agile teams avoid burnout.

Legacy systems grow through adapters and wrappers into technical debt. Modernization rarely pays off in the short term, so few companies dare to start.

No-code testing is still needed. The platform covers the lower test levels, but the higher ones stay, and citizen developers rarely test their own apps.

There is always more than one reason behind what we do at work, some external, some internal. Asking why you really do it breaks unconscious routines.

Individuality brings two challenges: social media distorts which opinions seem common, and endless decisions drain us, self-organization included.