
On-Site Testing Conferences: Why Networking Needs Presence
Istanbul's software testing conference grew from a risky debut to an event linking testers of Europe and Asia, with translation in every track.
Listen to expert conversations about software testing, test automation, AI in quality assurance, and modern development practices.

Istanbul's software testing conference grew from a risky debut to an event linking testers of Europe and Asia, with translation in every track.

Mutation coverage measures how many deliberately planted bugs your tests catch. It says more than code coverage, especially when AI agents write tests.

More test automation does not mean better quality. Why flaky AI tests, missing strategy, and the wrong roles quietly hollow out your test suite.

AI coding agents need fewer manual reviews once you work on the system itself: rules, hooks and retro skills make their corrections stick for good.

Agentic systems are not just agents working alone. Between 8 and 12 agents can cover testing end to end, but humans still judge what AI cannot.

More AI-generated code means more defects, and only about 30% of AI review comments help. Static analysis, test selection and reviews must scale too.

AI in software testing leaves a faulty fraction: hallucinated requirements, invented test cases. Business knowledge keeps expert testers in demand.

The ISTQB boards of Germany, Austria and Switzerland share one back office, which has kept their volunteer work running for up to 20 years.

Lean management starts with understanding a problem instead of rushing to a quick fix. That breaks the repeat cycle and exposes waste teams overlook.

A Quality Sprint tackles persistent quality issues in one workshop day with all stakeholders, ending in three to four next steps with clear owners.

Performance monitoring catches slowdowns users abandon after five seconds. Alerts, AI log analysis and a small replica find the exact query at fault.

Even 100% branch coverage let an off-by-one bug slip through. Coverage is only as good as its assertions, and loops need several iterations.

End-to-end test automation stays maintainable with a dedicated HTML test attribute, a central mapper, a three-layer framework and one naming convention.

LLM testing can be automated if you accept non-determinism: rubrics and acceptance ranges replace yes/no asserts, and a calibrated LLM judges outputs.

API testing depends on the protocol: REST, GraphQL, webhooks or MCP. It runs more stably than browser testing, and agent-friendly APIs save tokens.

Resilience in software projects starts with accepting bugs rather than avoiding them. What bacteria and moths teach about trends and testing hypotheses.

LLMs in software testing pay off where language is the raw material: keyword docs, rule-based reviews, defect messages. Reasoning models review better.

Vibe coding risks grow where system understanding is missing. The future belongs to Pi-shaped developers who combine breadth with real depth.