Automation of testing activities, including strategy, frameworks, tool selection, maintainability, and appropriate automation boundaries.
Explore software quality assurance's role in low-code testing. Ensure your projects meet high standards without sacrificing speed.
Explore test automation strategies for desktop, client-server, and web applications, ensuring effective testing across system types.
Boost efficiency with agile test automation. Experience structured implementation phases and enhance your project outcomes
Explore various test automation approaches, from model-based to keyword-driven testing, and choose the right strategy for your needs.
Enhance your quality assurance with test automation. Discover how automated testing tools boost efficiency in software development.
Use test automation tools to streamline routine tasks efficiently and gain more time for agile testing techniques.
Get effective test automation tools suggestions to enhance testing efficiency and quality. Discover what works best for your team!
COBOL developers said writing unit tests in Java was easier than in their own language. Here's the interface architecture that made that possible on a 60-year-old mainframe.
From developer to test automation engineer: Why clean code principles decide which automation lasts for years and which doesn't.
Playwright works just as well with Python as with TypeScript. Here's what changes, what you gain, and what you have to build yourself.
130 participants, a clear focus on test automation and real practical reports: Why TACON in Leipzig attracts more and more people every year.
Test automation code deserves the same design care as production code. Page Object, Builder, Facade and why skipping design patterns turns frameworks into spaghetti.
Robot Framework started as a master's thesis in 2004 and now has over 80 foundation members. Here's how a generic test core scales to a global ecosystem.
From two weeks of manual testing to three hours: how an AI-based solution automates legacy apps without element IDs.
A gaming company logged nearly 5,000 defects in eight weeks. Better test automation strategy, not better tools, is how you change that picture.
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.
Switching test automation frameworks mid-product is messy. Here is what a real Cypress-to-Playwright migration looks like, from the pricing clash that forced the move to AI-assisted test translation.
Playwright or Cypress for component and end-to-end testing? Which tool has the edge today and when a change is really worthwhile.
Insurance salespeople test releases themselves - with the right tools and coaching, it works. How a Center of Excellence can do this in three minutes per release.
If you calculate target values for 2,500 signals manually, you lose the connection. How a reference implementation as a test oracle solves this.
32.000 Slack members, 700 libraries, a budget of 250,000 euros a year: how Robot Framework remains so vital as an open source project.
Migrating Cypress to Playwright: Why a team hackathon with 7 tools made the obvious choice the sure thing.
Those who test don't protect themselves, they protect everyone. How a test network works in embedded development and why CMake, Google Test and a self-built automocker are the key.
700.000 lines of code in a combi steamer, 2,000 test cases per night: how test automation really works in device development.
AI-generated test code that compiles but tests the wrong thing: Why writing unit testers yourself and having business code generated instead is often the smarter approach.
Pen tests at the end of a project always find the same things: headers, misconfigurations, standard gaps. Integrating security into the pipeline reduces this to 4 to 5 really critical findings.
Testing embedded software without having the hardware? How unit tests, CI pipelines and MISRA standards interact in practice.
90% of failed tests are real bugs, not automation errors. Why no project can do without manual testing.
AI testing, test data, accessibility: which trends testers should really have on their radar and why the right tool often doesn't solve the actual problem.
A test automation monolith that has grown for years, XML everywhere in the code like a tumor: How to refactor anyway and what really counts.
Which E2E framework really suits your project? If you clarify the requirements first, you'll make the better choice - and save yourself the expensive switch afterwards.
Throwing away four years of test automation and starting from scratch: Why this radical cut was the right decision and what was done differently this time.
6.000 test cases, CI runtime under 10 minutes: How test-based selection via code coverage makes exactly that possible.
Agile quality needs more than test automation: roles, approach and processes must fit together. The House of Agile Quality shows you where to start.
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.
6.5 hours of test runtime, reduced to 10-15 minutes: How test case selection across C++ and Java makes it possible.
Selenium is not a test tool, but a browser automation. Why this difference determines how you integrate test automation into your team.
200 failed tests, but only seven real causes: How machine learning radically simplifies testing operations without rationalizing away roles.
