Skip to main content

Search...

Podcast: Software Testing, AI and Quality Insights : Page 10 of 16

Migrating from Cypress to Playwright: The Real Effort
Migrating from Cypress to Playwright: The Real Effort

Migrating from Cypress to Playwright: The Real Effort

Migrating from Cypress to Playwright took a team over a year alongside daily QA. The main hurdles: session handling, request interception, legacy tests.

AI Test Description: Test Cases Structured Like Code
AI Test Description: Test Cases Structured Like Code

AI Test Description: Test Cases Structured Like Code

An AI test description makes AI systems testable: five capabilities and quality criteria like correctness and bias turn standards into concrete tests.

Tester Stereotype: Only 6 Percent Fit the Mold
Tester Stereotype: Only 6 Percent Fit the Mold

Tester Stereotype: Only 6 Percent Fit the Mold

Only 6% of surveyed testers fit the tester stereotype. Many come from boatbuilding, theater or urban planning, and degrees barely predict their roles.

CI/CD Pipelines in Embedded C: Tests as a Safety Net
CI/CD Pipelines in Embedded C: Tests as a Safety Net

CI/CD Pipelines in Embedded C: Tests as a Safety Net

CI/CD pipelines for embedded C at Marquardt run on CMake, Google Test and generated mocks. Every bug fix starts with a test that reproduces the bug.

Testing Trends: Testing AI and Testing with AI
Testing Trends: Testing AI and Testing with AI

Testing Trends: Testing AI and Testing with AI

Trends in software testing: AI is used most in programming and testing, far less in requirements engineering. Scrum dominates, even in aviation.

Accessibility Act: Blind Testers Find What Tools Miss
Accessibility Act: Blind Testers Find What Tools Miss

Accessibility Act: Blind Testers Find What Tools Miss

Accessibility testing can't be fully automated. Accessible components can still break once combined, and blind testers catch it with screen readers.

Software Analysis: Assessing an Inherited Ticket Shop
Software Analysis: Assessing an Inherited Ticket Shop

Software Analysis: Assessing an Inherited Ticket Shop

Software analysis of an inherited ticket shop: static analysis gave a first verdict in 1.5 days. Then a third of the code turned out to be a black box.