AI Briefing#qa
The latest AI and developer news about #qa, with the original source and a short summary.
The latest AI and developer news about #qa, with the original source and a short summary.
The average test design period was reduced to 1.4 days through code-based analysis.
The tool converts one-time LLM-driven browser explorations into deterministic scripts that cost nothing to run in CI.
The Yeogi-eottae QA team shared how their verification methods and perspectives changed when transitioning from exhibition QA to reservation and settlement QA.
The Toss QA team shifted hotfix decision criteria from priority to go/no-go status to align with gradual rollout environments, introducing an AI-based crash reproduction tool and an automated logging system.
Toss has built its own platform, Tossion, which integrates QA data and AI-based release verification.
By splitting documents and rules into smaller injections, Gemini-based TC automation became a practical part of daily work.
To reduce wait times, Self-POS was designed by rebuilding state management, validation, and hardware from the ground up.
QA directly cut off DB, cache, and queue connections to verify customer experience and post-recovery data consistency.
Supports generation and maintenance of validation code via natural language prompts, with integration into CI/CD pipelines.
Operators create missions with a DSL, and the LLM generates and validates drafts.
A client programmer is responsible not just for code, but also for tools, resources, and collaboration.
Oliveyoung has adopted chaos engineering, which intentionally induces failures to test system resilience, in order to improve service stability.
Oliveyoung has built and operates automated testing centered on CSP, the core user path, to improve service stability.
QA creates core value by minimizing product defects and helping facilitate smooth communication between developers and users.
Banksalad's QA team unveiled a method for automatically generating complex MyData test data using LLM and prompt engineering.
A proposal has been presented for using generative AI to automate the QA process from requirements analysis to defect analysis, boosting efficiency.
They dropped the Slack bot that required human intervention and switched to deployment-triggered automation.
Automation and API understanding greatly improve QA's efficiency and test coverage.
By addressing WebView handler issues and CI/CD environment differences, the team lowered the failure rate of Android UI automation.
Applying Sorry-Cypress parallel testing reduced E2E execution time from over 2 minutes to the 30-second range.
Devsisters' Web Service Cell adopted a JIRA-integrated tool to overcome the limitations of Excel and improve its test management process.
This article shares a case study of building Angular E2E tests by migrating from Protractor to Cypress to overcome Protractor's limitations and improve test reliability and execution speed.
The Cookie Run: OvenBreak team adopted JIRA as a company-wide issue management tool to overcome the limitations of spreadsheets and Trello.
This presents a logical way for QA to respond to issues that developers claim are 'spec' in order to improve quality.