1 views collected around this technical thread.
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.
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.
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 advanced Jenkins course covers pipeline builds, multi-node configuration, plugin development, distributed builds, integration with tools like SonarQube and Artifactory, and continuous deployment, providing practical video tutorials and resources for mastering CI/CD workflows.
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.
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.
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 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.
Unmanned MOCK automatically generates intelligent, context‑aware mock responses for downstream services in end‑to‑end tests by collecting sub‑call data, extracting knowledge, and applying dynamic rules, so failures in downstream systems are isolated, raising test success rates toward near‑100 % without manual mock configuration.
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.
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 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.
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%.
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.