1 views collected around this technical thread.
This article explores iQIYI’s comprehensive testing ecosystem, detailing industry trends, the platform’s multi‑terminal challenges, fragmented legacy solutions, and the unified, cloud‑native “Qijing” environment that streamlines test access, zero‑trust security, and real‑world validation for rapid product delivery.
This article presents ten actionable recommendations—including using layered abstractions, prioritizing testability, running tests frequently in CI, adhering to the test pyramid, adopting Page Object and BDD patterns, understanding AI, selecting appropriate tools, and investing in training—to dramatically improve the effectiveness and maintainability of automated testing in software projects.
The article outlines China’s 2024‑2027 information‑technology standards initiative, the DevOps continuous‑testing maturity model released in 2023, its five‑level capability framework, and showcases early evaluation results from major banks, highlighting improvements in automation, defect prevention, and end‑to‑end quality assurance.
This article examines how Kuaishou’s internal Mulan universal code analysis service tackled pipeline quality challenges by introducing on‑demand triggering, incremental checking, and unified rule infrastructure, resulting in dramatically faster static checks, lower rule‑development costs, comprehensive monitoring, and a rapid increase in rule coverage.
This guide outlines a step‑by‑step method for recognizing critical APIs, evaluating their importance and complexity, assigning priority levels, and preparing the necessary people, tools, and CI/CD processes to implement effective API automation testing.
The article reflects on a bug‑fixing team's experience, arguing that bugs are an inevitable by‑product of software development, discussing the limits of zero‑tolerance policies, the trade‑offs between quality and resources, and suggesting cultural and engineering practices such as testing left‑shift, code reviews, and refactoring to improve quality without sacrificing delivery speed.
The article describes a reflection‑based workflow that lets an AI iteratively generate, validate, and refine Go unit tests until 70 %+ code coverage is reached, using coverage‑out parsing, role‑based prompts, and automatic error correction, enabling fully autonomous test creation that can be integrated into CI pipelines to dramatically improve developer productivity.
The article argues that despite advances in tools and practices, modern software quality has declined over the past ten years due to factors such as increasing complexity, lack of focus, superficial engineering culture, and inadequate attention to reliability, usability, and security.
This article explains the importance of code review, outlines its core goals and basic principles, provides step‑by‑step practical guidance with a detailed checklist, shares real‑world case studies and code examples, and discusses metrics and future AI‑assisted improvements to help teams improve software quality.
This article explains the importance of code review, outlines its core objectives and basic principles, describes practical steps and a detailed checklist, shares several real‑world case studies with before‑and‑after code snippets, and discusses the benefits, metrics, and future AI‑assisted enhancements.
The article details China’s push for integrated R&D‑operations through DevOps, highlights the ITU‑T Y.3525 international standard, and showcases how leading banks and financial firms achieved Level 3 Continuous Testing assessments, illustrating the impact on software quality, automation, and delivery efficiency.
The article presents a comprehensive framework for evaluating engineering productivity by separating efficiency (speed and quality) from effectiveness (usability), reviewing academic literature, interviewing Google engineers, and proposing four interrelated types of software quality—process, code, system, and product—along with practical measurement challenges and recommendations for technical leaders.
This guide walks you through the fundamentals of API automation testing, from understanding HTTP basics and selecting tools, to building a Pytest framework, writing test cases and scripts, integrating tests into CI/CD pipelines, and continuously improving test results.
This article analyses the drawbacks of manual code review, explains why they arise, and presents a practical solution that embeds a large‑language‑model‑based AI reviewer into a CI/CD pipeline, detailing configuration steps, script examples, and the resulting efficiency and quality gains.
This article explains the drawbacks of manual code review, demonstrates how AI large‑model services can automate and improve review quality, and provides a step‑by‑step guide—including a Java script and CI pipeline configuration—to embed JD's Chatrhino model into a continuous integration workflow, resulting in higher efficiency, accuracy, and reduced development cycle time.
The article outlines practical principles and recommended coverage percentages for functional, boundary, security, performance, regression, integration, data management, and maintainability aspects of API automation testing, explaining why each level of coverage is essential for quality and efficiency.
The article recounts the author’s journey building and scaling front‑end UI automation for desktop, web, and mobile, exposing challenges such as fragile end‑to‑end tests, high maintenance cost, and merge‑induced regressions, and proposes a three‑layer strategy of unified frameworks, collaborative case sharing, and enhanced reporting that yielded 70% business coverage, 93% pass rates, and thousands of bugs discovered, while outlining future AI‑driven test generation.
This article explains how QA evolves from basic functional testing to holistic quality assurance, outlines the differences between testing and quality, and provides detailed, stage‑specific strategies—including process, automation, monitoring, and risk management—to build sustainable quality systems for both mature iterative and short‑cycle business models.
The article analyzes why test scenarios often lack full coverage, identifying both subjective causes such as carelessness and insufficient knowledge, and objective factors like tight schedules and low‑fidelity test environments, then proposes pre‑, during‑, and post‑testing strategies to enhance coverage.
This article explains the evolution of software development and operations in China, introduces the Continuous Testing concept and its five‑level maturity model, details each phase from requirements to feedback, showcases real‑world assessments by major banks and securities firms, and announces the 2024 Continuous Testing capability evaluation program.