The article explains how turning vague, experience‑based software tasks into measurable, structured processes enables AI to run autonomous improvement loops, creating a self‑reinforcing flywheel that boosts productivity while highlighting the necessary engineering infrastructure and real‑world constraints.
When over 90% of a codebase is produced by AI, the authors show how a unified "people‑align → human‑machine‑align" approach, driven by evaluation agents, transforms technical debt into incremental business work, enabling continuous refactoring, AI‑friendly standards, and a sustainable engineering environment.
The AC/DC framework reimagines software development by moving verification from post‑commit CI pipelines to the moment code is generated, letting AI agents write, check, and fix code in a self‑correcting loop, while redefining human engineer responsibilities.
The article details how a three‑engineer team used OpenAI's Codex agents to generate an entire production‑ready software stack—including over a million lines of code, 1,500 pull requests, and a full CI/CD pipeline—in roughly one‑tenth the effort of manual coding, while describing the architectural, operational, and organizational adjustments required for such agent‑first development.
This article analyzes how the AutoResearch method pioneered by Andrej Karpathy was adapted to software development, detailing three key enhancements—multi‑agent cross‑review, a five‑dimensional scoring system, and feedback‑driven iteration—that enable a fully autonomous pipeline capable of completing a medium‑complexity issue in about ten minutes with a 9.0/10 code quality score.
The article deeply compares shift‑left testing with traditional testing across five dimensions—goal orientation, participants, timing, technical means, and quality metrics—showing how early defect prevention, cross‑functional collaboration, embedded quality checkpoints, automation, and measurable outcomes can dramatically reduce defects and accelerate delivery.
This article details how Karpathy's AutoResearch methodology was transferred to software development, introducing multi‑agent cross‑review, a five‑dimensional quantitative scoring system, and feedback‑driven iteration to build a fully automatic pipeline that resolves a medium‑complexity GitHub Issue in about ten minutes with a 9.0/10 code‑quality score.
This article analyzes why software deployment failures pose systemic risks, enumerates the most common root causes, and explains how AI‑driven automation—covering intelligent version control, automatic rollback, test optimization, dependency management, database migration, observability, security checks, self‑documenting pipelines, backup verification, and predictive scaling—can transform DevOps from reactive firefighting to proactive, self‑healing delivery.
The article explains why the last mile of software delivery—merging, testing, changelog, version bump, documentation sync, and retrospection—is often the bottleneck, and introduces three automated skills (/ship, /document-release, /retro) that institutionalize these tasks to create a closed‑loop workflow.
The article examines why most companies are still at the proof‑of‑concept stage for AI‑enabled testing, outlines three practical pillars—data, scenario selection, and closed‑loop feedback—and warns of common pseudo‑AI pitfalls through concrete industry case studies.
The article explains how AI‑powered agents change software delivery, why traditional notions of task completion no longer apply, and how a Fitness Function‑based harness engineering approach—illustrated with the Routa project—encodes executable, auditable completion criteria, hard‑gate checks, and contract consistency to reliably guide agents through the development loop.
Over five months the team created an internally used product from an empty Git repository, writing every line of application logic, tests, CI configuration, documentation and tooling with OpenAI's Codex, achieving roughly one‑tenth the effort of manual coding while uncovering new engineering roles and processes.
OpenAI’s five‑month "Harness Engineering" experiment showed that a three‑person team could generate a million‑line software product entirely with Codex and GPT‑5, achieving ten‑fold productivity, redefining engineering roles, workflow loops, and offering five practical guidelines for AI‑augmented development while highlighting unresolved challenges.
The article explains how shift‑left testing embeds quality responsibility early in the software lifecycle, outlines its three dimensions, shares a fintech case that cut regression defects by 51%, warns against common pitfalls, and explores emerging AI‑augmented practices.
This article explains what smoke testing is, why it’s essential for early defect detection, outlines step‑by‑step implementation, highlights its efficiency and risk‑reduction benefits, and shows how it fits into agile, CI, and large‑scale projects.
The article breaks down seven empirically validated levers—spanning cloud test infrastructure, AI‑driven test case engineering, asynchronous workflows, a re‑balanced automation pyramid, real‑time quality dashboards, shift‑left security gates, and a unified digital collaboration platform—that together boost remote testing efficiency and reduce defect escape rates despite rising distributed team adoption.
When business requirements evolve quickly, API automation testing becomes a critical safety net, offering rapid regression detection, faster delivery, and a living contract for services, but it must be designed with resilient patterns, layered coverage, and health metrics to stay effective.
The article presents a four‑dimensional agile testing framework for fast‑paced game development, detailing a risk‑matrix‑driven pipeline, player‑behavior twin testing, and concrete practices such as hot‑update safety nets and data‑driven test case generation, while showcasing a real SLG project’s efficiency gains and future AI‑driven testing directions.
The article presents ThoughtWorks' comprehensive agile testing framework, detailing QA roles, core principles, and step‑by‑step practices across iteration development, story‑card workflows, and product‑environment activities, while emphasizing early testing, automation layering, and continuous quality feedback.
The article explains how the Ralph loop, a minimalist bash for‑loop design introduced by Geoffrey Huntley, lets Claude Code repeatedly execute tasks until completion, offering a simpler, more reliable alternative to elaborate multi‑agent orchestrations for quantifiable, verifiable programming work.
Maven 4, now in its fifth release candidate, introduces a new POM model version 4.1.0 with backward compatibility, separates build and consumer POMs to eliminate POM pollution, adds explicit artifact types for classpath and module jars, renames modules to subprojects, and brings a tree‑based lifecycle for true parallel builds, all supported by an official upgrade tool.
This article walks through a complete CI/CD workflow for teams that ship software frequently, covering feature branching, peer review, automated QA, pre‑production staging, and production deployment with canary and blue‑green strategies, while sharing practical tips and common pitfalls.
This article explores proven strategies for reducing technical debt, showing how short‑term debt repayment can accelerate developer productivity, deliver business value, and improve team morale through concrete examples from Atalasoft and Trello.
This article introduces a test‑driven AI programming loop that tackles the “last‑mile” problem of AI‑generated code by adding automated acceptance, self‑testing, bug fixing, and continuous iteration, demonstrated through a favorite‑count feature repair case and outlining future enhancements.
Leveraging AI and natural language processing, Tmall’s quality assurance team transformed traditional manual testing into a semi‑automated and fully automated pipeline—covering requirement analysis, test case generation, data construction, execution, and validation—resulting in significant efficiency gains, traceability, and continuous improvement across multiple business lines.
This guide shows non‑coding test engineers how to understand CI (continuous integration) and CD (continuous deployment), why they’re not exclusive to developers, and three practical actions—business‑scenario requirement submission, targeted testing of generated builds, and rapid feedback—to turn CI/CD into an efficiency partner.
This article explains how Alibaba's WaterFlow, an AI‑driven end‑to‑end development platform, tackles the high demand volume, diverse tech stacks, and slow collaboration of Taobao's recommendation feed, enabling many features to be delivered in just two days instead of a week.
The article explains how the single‑commit review mode in Alibaba Cloud Codeup uses AI to evaluate each commit individually, addressing the shortcomings of default bulk diff reviews, detailing configuration steps, recommended scenarios, observed benefits, and its performance trade‑offs.
This article outlines how a team tackled long‑standing automation gaps in custom output modules and second‑party packages by introducing a lightweight interception verification system and a Groovy‑Spock data‑driven testing framework, achieving full‑coverage regression in minutes, reducing bug detection time, and boosting overall testing efficiency.
DevOps, emerging from the need to resolve conflicts between development and operations, combines agile practices with automation, continuous integration, delivery, infrastructure as code, monitoring, microservices, and collaboration to create a seamless, reliable software delivery pipeline that aligns teams, speeds releases, and improves system stability.
This article details Qunhe Technology's shift from traditional post‑test bottlenecks to a proactive automation left‑shift strategy, outlining fragmented environment issues, integrated toolchains, AI‑driven test selection, and measurable efficiency and quality gains across performance, interface, and UI testing stages.
Facing frequent requirement changes in fast‑moving agile development, testing teams must adopt adaptive processes, modular automation, cross‑functional collaboration, and AI‑driven tools to maintain quality, reduce maintenance costs, and turn testing from a reactive bottleneck into a proactive quality driver.
This guide walks through a complete automated deployment workflow—including Maven build, rsync transfer, graceful shutdown of Nginx and Eureka services, service restart, health checks, and final bring‑up of both Eureka and Nginx—using shell commands and parameterized variables.
This article explains how test automation boosts efficiency, reliability, and speed in software development by eliminating repetitive manual tasks, improving test coverage, and enabling rapid feedback through continuous integration, while providing a practical five‑step roadmap and a Selenium code example.
This article traces the history of Perl's CPAN from its 1995 origins, explains how its centralized module repository and automated testing infrastructure pioneered package management, and shows how CPAN's concepts spread to Python, Ruby, Java, and JavaScript, ultimately influencing the massive npm ecosystem.
The article introduces an AI‑driven automated testing system that streamlines code self‑testing, improves impact assessment, and generates comprehensive test reports, detailing its modular architecture, workflow, AI test engine, and future enhancements such as UI simulation and AI‑generated unit tests.
Static testing, a proactive quality assurance method that examines code and documentation without execution, helps detect defects early, reduces repair costs, improves code readability, and complements dynamic testing, with techniques ranging from inspections and walkthroughs to automated tools like SonarQube, CheckStyle, and ESLint.
Agile testing transforms software quality by embedding testing throughout development, emphasizing shift‑left practices, automation, and close collaboration between developers and QA, with detailed guidance on testing quadrants, sprint vs release strategies, and practical steps to achieve faster, more reliable product delivery.
The article explains TDD’s core three laws, its rapid feedback loop, common implementation challenges with practical solutions, ways to enhance effectiveness through BDD, CI, and static analysis, and the long‑term benefits of reduced technical debt and improved code quality.
KuJiaLe's testing team curates ten influential 2024 technical articles covering AI‑driven test case generation, AI‑assisted code review, lead tester training, Greasemonkey efficiency, custom mock platforms, private vs. public LLMs, FastGPT knowledge bases, CI bottleneck solutions, front‑end release strategies, and construction‑drawing regression testing.
This article details how KuJiaLe's front‑end publishing platform was redesigned to solve chaotic environments, low‑efficiency releases, and poor quality by introducing standardized workflows, modular management, automated quality checkpoints, and future automation plans, resulting in dramatically higher on‑time delivery and stability.
The article details China Information and Communication Research Institute's dual ITU DevOps international and domestic standard assessment, Zhongdian Hongxin's successful certification, the practical benefits of end‑to‑end toolchains, and insights from company leaders on future DevOps development.
This free Jenkins collection offers beginners a comprehensive set of seven resources—including books, notes, mind maps, interview questions, and detailed guides—covering everything from basic installation to advanced CI/CD pipelines, with a full table of contents and QR code for instant download.
This article explains what DevOps and artificial intelligence are, explores how AI can enhance DevOps processes such as continuous integration, monitoring, and security, and discusses the limitations and challenges of combining these technologies.
This article outlines a four‑layer architecture for automated testing frameworks and describes the essential layers of a DevOps automation efficiency platform, covering system under test, core architecture, script organization, user management, and resource, data, capability, pipeline, and user layers.
The article presents a comprehensive overview of Google’s code‑coverage system, describing its metrics, integration into the daily development workflow, underlying infrastructure, visualization tools, data‑driven analysis of five years of coverage data, and developer survey results that reveal adoption patterns and perceived usefulness.
The article outlines Google’s release engineering principles, roles, and processes—including self‑service, frequent high‑speed releases, sealed builds, policy enforcement, configuration management, and the Rapid system—to illustrate how automated, reliable software delivery is achieved at scale.
This article provides an in‑depth, side‑by‑side analysis of Jenkins and GitLab CI/CD, covering their histories, core features, community support, pros and cons, and practical guidance to help DevOps teams choose the most suitable continuous integration and delivery platform for their projects.
This guide details a comprehensive set of software development metrics—including agile velocity, code quality, continuous integration, technical debt, unit and smoke testing, test automation, quality process, and continuous delivery—explaining their definitions, data sources, calculation methods, reference standards, and responsible platforms to help teams monitor and improve performance.
The article reviews the history of China's IT industry over the past eighteen years, exposing how government policies, CMM certifications, and superficial agile practices have led to chronic software quality and delivery problems, and argues that only solid fundamentals such as extreme programming, TDD, and deliberate practice can truly improve software development.
This guide explains where to place software quality gates in the development workflow, compares absolute and relative targets, distinguishes hard versus soft gates, and offers practical criteria for designing fast, robust, and easily fixable checks in pull requests and nightly builds.
This article outlines the background, step‑by‑step implementation plan, execution mechanisms, sustainable maintenance practices, and measurable outcomes of introducing API automation testing to ensure high‑quality iterative development and stable online services.
Over the past two decades, software engineering has shifted from waterfall to agile, embraced DevOps, cloud and micro‑services, containerization, CI/CD, open‑source, AI, heightened security, diverse languages, remote collaboration, user‑centered design, dependency management, and continuous learning, while core concepts such as requirements analysis, design principles, testing, version control, and architecture remain unchanged.
vivo’s CICD artifact management has evolved from manual builds to a comprehensive Platform Management 2.0 that provides unified storage, multi‑type support, version control, promotion, security scanning, lifecycle policies, and fine‑grained access, dramatically reducing errors and operational costs.
The article outlines essential DevOps and agile practices—including Scrum, Kanban, continuous integration, continuous delivery, monitoring, micro‑services, automation, and security—to improve collaboration, increase release frequency, and deliver higher‑quality software faster.
This article examines the evolution of UI automation in a large‑scale frontend environment, detailing early expectations, framework choices, practical challenges, and a comprehensive set of process, tooling, and reporting improvements that together boosted test coverage, stability, and team efficiency while highlighting the ongoing trade‑offs between automation value and maintenance cost.
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.
The author recounts his early DevOps experiences with continuous integration using TFS, PowerShell, and Azure, reflects on the current undervaluation of DevOps, reviews the “Jenkins 2.x Practical Guide” and highlights sociological insights and practical challenges of adopting CI/CD pipelines.
This comprehensive guide walks you through Makefile fundamentals, covering basic syntax, variables, pattern rules, automatic variables, functions, conditional statements, multi-target handling, phony targets, debugging techniques, and advanced custom functions to help you automate and streamline complex build processes.
This article provides a comprehensive overview of DevOps history and principles, explains continuous integration concepts and benefits, compares popular CI tools such as Jenkins, GitLab CI/CD, Travis CI, Azure DevOps, and CircleCI, and demonstrates how to implement pipelines in Jenkins using both declarative and scripted syntax.
This article examines how automation testing can boost software delivery efficiency within DevOps by outlining its relationship with DevOps, reasons for adoption, practical goals, implementation steps, measurement metrics, and emerging trends such as AI, big data, cloud, security, and low‑code tools.
This article details Shentong's systematic approach to improving test completeness, covering test case design, a custom Quality Keeper workflow, code‑coverage measurement, precise regression strategies, automation effectiveness, issue‑driven optimization, and future plans such as front‑end coverage and AI‑assisted testing.
This article examines how Shentong, a logistics company, built a comprehensive mobile testing ecosystem—including functional, compatibility, and specialized tests—leveraging automation, a DevOps‑driven packaging pipeline, and a Jenkins‑based framework to dramatically improve testing efficiency and product quality.
This guide explains what SonarQube is, its advantages, architecture, and provides step‑by‑step Docker installation, project setup, scanner configuration, and real‑world examples of detecting unreachable code and unused parameters.
To meet NetEase Cloud Music’s tight regression schedule, the team built Athena, a one‑stop UI automation framework that combines record‑and‑play case entry, Dawn telemetry‑based stable element locating, white‑box communication for efficiency, and integrated network‑mock and multi‑account support, delivering 73% coverage, over 90% success, and cutting regression time by more than 60%.
The article traces the evolution of software delivery from early lean and continuous‑integration tools through the rise of DevOps, cloud, SaaS, and container orchestration, highlighting how growing scale and complexity gave birth to platform engineering and a shift‑left mindset for developers and ops teams.
This article explains the background, challenges, core concepts, automation techniques, toolchain, process improvements, and practical implementation steps of continuous integration (CI) for traditional enterprises, highlighting benefits such as higher software quality, faster feedback, reduced risk, and more efficient team collaboration.
The article examines why software testing inevitably consumes time and resources, explains the limits of both manual and automated testing, outlines scenarios best suited for automation such as regression and performance testing, and warns against unrealistic expectations, unnecessary tests, and security blind spots.
Google’s software engineering practices—including a unified source repository, Blaze build system, rigorous code review, automated testing, continuous integration, and structured project and personnel management—are detailed, offering insights and comparisons for other organizations seeking to adopt similar high‑scale development methodologies.
This guide explains how to balance implementation cost, maintenance cost, monetary cost, benefits, and risk when designing a test plan or strategy, outlines the differences between single test plans and test strategies, and provides detailed questions and considerations for test content, coverage, tools, processes, and utility to help teams produce practical, cost‑effective testing documentation.
This article details how a rapidly expanding audio service built a lightweight, modular testing framework called FAST, defined core scenario‑based testing concepts, and implemented an automated pipeline that reduced manual effort, cut costs, and improved release quality across multiple teams.
The article explains how LinkedIn adopted the 10X thinking to transform its mobile development process, introducing aggressive goals, static analysis, distributed builds, rapid testing layers, and a weekly release cadence to dramatically improve engineering efficiency and product delivery.
The article explains why continuous testing of infrastructure is critical for stability and reliability, outlines a comprehensive testing scope ranging from unit to reliability tests, discusses tool selection and practical Terraform‑based examples, and shows how test‑driven development can improve IaC workflows.
This article presents a systematic approach to improving code quality across the software development lifecycle, covering traceability between tasks and commits, early static analysis, efficient code review, disciplined branching strategies, commit‑message enforcement, and fostering a collaborative technical culture.
This guide reviews the ten most popular CI/CD platforms—including GitLab, Azure DevOps, GitHub Actions, CircleCI, Jenkins, Travis CI, Bitbucket Pipelines, TeamCity, Semaphore, and Harness—detailing their core capabilities, unique strengths, and key considerations to help teams select the right tool for streamlined software delivery.
This article introduces CI/CD as a DevOps approach, explains the challenges of selecting the right pipeline tool, and provides detailed overviews and key features of ten popular CI/CD solutions—including GitLab, Azure DevOps, GitHub Actions, CircleCI, Jenkins, and more—to help readers choose the best fit for their workflows.
The article explains that viewing testing as a mindset is essential for developers, outlines how to decide what to test—through user journeys, new features, and bugs—compares manual and automated testing, discusses the shift of testing responsibilities leftward, and clarifies who should own testing within various team structures.
The article explains why software testers should learn to write code, outlining twelve advantages of automated testing such as increased efficiency, higher quality, repeatability, better coverage, early defect detection, documentation, cross‑platform support, collaboration, real‑time feedback, stronger debugging, scalability, cost reduction, and competitive edge.
This article explains why efficiency matters in software delivery, introduces CI/CD concepts and tools like Jenkins and GitLab, details installing GitLab Runner, walks through pipeline configuration with key YAML keywords, and emphasizes that mastering DevOps principles and tools dramatically improves development productivity.
The 2022 China Enterprise Agile Practice Whitepaper, based on a survey of 644 companies across 43 cities and 16 industries, uncovers how agile adoption has surged, highlights dominant frameworks like Scrum of Scrums, identifies key engineering practices, and pinpoints organizational culture as the biggest hurdle for Chinese firms navigating digital transformation.
This article presents a detailed guide on implementing DevOps principles in frontend development, covering background challenges, pipeline architecture, workflow design, tool integration, and step‑by‑step practices to improve delivery efficiency, code quality, and team collaboration.
This article explains how to build a Jenkins-based continuous integration pipeline, covering Jenkins fundamentals, pipeline architecture, Groovy DSL components, task conversion, API interactions, deployment strategies, and performance considerations for reliable CI/CD operations.
The article explains how built‑in quality, a core principle of SAFe and lean‑agile thinking, integrates quality into architecture, design, code, system testing, and release processes to enable fast, reliable delivery of software and hardware solutions while reducing rework and compliance risk.
This article explains the concepts of DevOps and CI/CD, describes continuous integration, delivery and deployment, illustrates their relationship, and outlines how enterprises can adopt CI/CD pipelines using tools like Jenkins, Kubernetes, Helm, and Argo CD.
China Information & Communication Research Institute’s recent DevOps assessment highlighted that China Merchants Securities’ TianGong R&D Management Platform earned excellent ratings in both pipeline and build‑integration modules, showcasing how standardized tools and end‑to‑end workflows can dramatically boost development efficiency, quality, and digital transformation in the financial sector.
This article explains how treating infrastructure as code changes the way continuous integration and delivery pipelines are designed, highlighting differences in source control, testing, automation, security, cost estimation, and deployment compared to traditional application development CI/CD practices.
This article explains the concept, significance, and practical case studies of MLOps—showing how integrating DevOps principles with data and machine learning creates reliable, automated pipelines for data quality, model monitoring, error analysis, and continuous integration, ultimately accelerating AI delivery.
Baidu’s AI‑driven, risk‑based testing framework automatically identifies high‑risk projects, allocates tasks, defines precise test scopes, and localizes defects using white‑box analysis and quality‑score models, cutting test‑case volume by up to 90 % and reducing release‑gate time from 50 hours to two, dramatically improving efficiency and defect recall.
Baidu’s AI‑driven risk‑based testing platform automates task allocation, precisely scopes test coverage, dynamically optimizes execution, and uses real‑time logs to locate defects, enabling a quality‑assessment model that blocked 1,123 unsafe releases, intercepted 318 bugs, saved over 2,000 person‑days, and cut assessment time from 50 to 2 hours, demonstrating that AI‑guided decisions markedly improve testing efficiency and delivery quality.
This article examines Baidu's risk‑driven, AI‑enhanced approach to unmanned software delivery, detailing the evolution of testing automation, the three human dependencies it eliminates, and the essential capabilities—comprehensive testing, stable builds, and precise risk evaluation—required to free testers from manual intervention.
This article explains the fundamentals of DevOps and CI/CD, detailing their definitions, the roles of Continuous Integration and Delivery, their relationship, and practical steps for enterprises to adopt CI/CD pipelines using tools like Jenkins, Kubernetes, Helm, and ArgoCD.
This article presents a comprehensive guide to using Subversion (SVN) for multi‑branch version control, covering branch management, daily development cycles, hot‑fix procedures, conflict resolution, and step‑by‑step setup and merge operations to streamline development and testing workflows.
This article explains the stages of the DevOps lifecycle—planning, coding, building, testing, releasing, deploying, operating, and monitoring—along with the popular tools used at each phase to enable continuous integration, delivery, and deployment.
In this firsthand account, a technical leader describes how adopting the Apifox API testing and mock tool transformed their small company's development workflow, cutting interface testing, integration, and client support times dramatically while improving code quality and overall team efficiency.
The article clarifies common misconceptions about DevOps, explains that true development‑operations integration relies on dedicated ops teams, automation tools, standardized delivery artifacts, and unified permission management rather than developers performing ops tasks, and highlights Google SRE practices as a practical guide.
This article explains what DevOps is, why it matters, and presents nine practical best‑practice recommendations—including culture, CI/CD, testing, observability, automation, security, and IaC—while also highlighting common anti‑patterns to avoid for successful DevOps adoption.
The article details a large‑scale C++ team's unit‑testing workflow, explaining why tests matter, how they set up cross‑platform macOS/Linux environments, adopt Google gtest/gmock with a custom Frida‑based mock, enforce coverage via gcov/lcov, compute incremental coverage, integrate Valgrind, follow deterministic test design principles, avoid common pitfalls, and embed the stable pipeline into CI gates and notifications.
This article explains the fundamentals of scalable CI/CD pipelines, covering their definition, four core stages, key attributes for a high‑quality pipeline, and multiple practical examples across microservices, containerized, serverless, and cloud‑based environments.
This article introduces Tox as a virtualenv manager and command‑line testing tool for Python, explains how to install it, set up a simple project with test and setup files, configure tox.ini, run tests across multiple Python versions, and customize environments for advanced usage.
This article explains how the ICBU low‑code platform’s rendering engine achieves high test coverage by linking each issue to a dedicated unit test and demo, using custom npm scripts, pre‑build cleanup, and a traceable changelog to improve code stability.
