This article presents an engineering‑focused methodology for designing, implementing, and maintaining a concurrent automated testing framework that supports mobile and web platforms, covering requirement analysis, technology selection, solution design, implementation details, and ongoing maintenance.
The article introduces JD’s iOS Mocker, a server‑side mock service that decouples client development from backend progress, provides comprehensive mock data for all shopping‑flow interfaces, improves testing efficiency, ensures UI robustness, and outlines its architecture, usage workflow, and future extensions.
This guide explains how to define custom Spring Boot properties, load them with @Value, reference other properties, generate random values, override settings via command‑line arguments, and manage multiple environment profiles, complete with code samples and testing tips.
This article details how Alibaba's RDC platform combines layered automated testing, test‑driven continuous delivery, and comprehensive online quality monitoring to overcome the myth of a single silver‑bullet solution in large‑scale software development.
The article explains why refactoring is essential for maintaining and evolving legacy code, defines refactoring, outlines when to start and stop, lists prerequisites, describes a step‑by‑step process with testing and version control, and connects refactoring to design principles and large‑scale systems.
The article describes how a small development team adopts a three‑week periodic release cadence, improves demand management, resolves operational concerns, and standardizes configuration, environment, deployment, and testing processes to achieve continuous delivery with higher quality and lower coordination cost.
This article explains website accessibility, describes how people with visual, auditory, motor, and cognitive disabilities access sites, and provides practical guidelines—including semantic structure, color contrast, ARIA roles, form and table markup, keyboard navigation, media handling, and testing tools—to help frontend developers build accessible web pages.
The article explains how Docker, as a lightweight container engine, can address common testing environment problems such as data and environment isolation, bug reproducibility, and resource overhead by enabling easy image building, data separation, scalable services, and streamlined CI/CD workflows.
This article compiles practical advice from two seasoned engineers—Rebecca Murphey and Philip Walton—covering essential front‑end tools, module usage, testing, build automation, Git strategies, server‑side rendering, Node.js mastery, deep code understanding, browser spec vigilance, code reviews, teamwork, and the value of documenting learning.
This article explains why and how to expose a locally running server to the public internet using ngrok, demonstrates installation and usage steps including region configuration, compares it briefly with the open‑source localtunnel tool, and notes security considerations for development testing.
Continuous Integration (CI) enables teams to merge code frequently, automatically build, test, and deploy, improving software quality, accelerating bug detection, and supporting agile development, with practical examples from fir.im’s pipeline, branch strategy, testing suites, and visualization techniques for effective DevOps.
The article describes how a development team transitioned to short‑cycle, periodic releases, outlining the goals, benefits, operational concerns, and a comprehensive set of improvements—including testing strategy, configuration and environment management, and automated deployment pipelines—to maintain quality while increasing release frequency.
This article compiles a curated list of indispensable Java libraries—including Guice, OkHttp, Retrofit, JDeferred, RxJava, MBassador, Lombok, SLF4J, JUnitParams, Mockito, Jukito, Awaitility, Spock, and WireMock—providing concise descriptions and practical code examples to help developers choose the right tools for modern backend development.
This article surveys the essential JavaScript full‑stack development ecosystem, detailing runtime environments, popular IDEs, build automation tools, testing frameworks, performance utilities, and debugging solutions, guiding developers in selecting the right tools for efficient front‑end and back‑end development.
This article details Ctrip's engineering practice of building a mobile continuous delivery platform that automates integration, testing, release, and operation of hundreds of native, hybrid, and React‑Native bundles, addressing scalability, efficiency, and quality challenges through message‑driven architecture, bundle splitting, automated testing, and gray‑release strategies.
This article describes the background, terminology, design principles, and detailed implementation of Alibaba's Detail platform, covering modular architecture, front‑back separation, module refactoring, stability, testing, continuous integration, deployment structures, and real‑world use cases.
The article explains why rapid response is essential in modern software projects, critiques the drawbacks of waterfall development, and introduces agile practices such as short iterations, user stories, continuous integration, automated testing, and close collaboration to deliver value more efficiently.
This article explains the end‑to‑end process of creating, releasing, and testing Android hotpatches—including release workflow, required files, implementation steps, comprehensive testing strategies, user‑transparent deployment, and common pitfalls—to ensure bug fixes reach users without disruption.
The article examines common challenges in legacy continuous‑integration pipelines—long build times, unstable tests, and complex dependencies—and presents a systematic, Theory‑of‑Constraints‑based approach that includes parallelization, mocking, infrastructure upgrades, test isolation, contract testing, and monitoring to improve build speed, reliability, and overall delivery efficiency.
An in‑depth walkthrough of Oracle 12c R2 Sharding, covering its core concepts, architecture, environment setup across three virtual machines, detailed GSM and shard catalog configuration commands, test model, results, limitations, and troubleshooting tips for real‑world OLTP deployments.
This article explains the importance of problem localization for testers, outlines a systematic approach from user interface to database, and provides practical step‑by‑step techniques, case studies, and tips to improve bug detection, communication, and overall software quality.
The article introduces Cable, Qunar's internal continuous integration platform that combines automated static code checks, environment validation, rapid feedback, and flexible configuration to improve development efficiency, reduce release failures, and enhance overall product quality within a fast‑paced online travel business.
The article explains how Google test engineers tackle the challenges of maintaining and upgrading legacy systems by redesigning test infrastructure, reducing reliance on fragile end‑to‑end tests, and adopting lightweight, mock‑driven test cases that dramatically speed up verification while preserving defect detection quality.
This article introduces front-end automated testing, compares BDD and TDD approaches, reviews popular unit testing frameworks such as Mocha, Jasmine, and QUnit, and outlines integration testing tools like CasperJS, Nightmare, Nightwatch, and DalekJS, providing code examples and practical guidance for efficient test implementation.
This guide explains how to structure product development cycles using Scrum, detailing iteration lengths, backlog prioritization, planning game preparation, roadmap definition, requirement tracking, and effective collaboration between development and testing teams to deliver publishable versions consistently.
This article examines the challenges of testing a mobile advertising SDK—such as missing server environments, extensive protocol fields, and costly manual test case updates—and proposes a mock‑proxy strategy, a minimal‑case design approach, and full automation to improve coverage and efficiency.
This guide outlines essential Android security testing checkpoints, covering network communication risks, data storage protections, and packaging integrity measures to help developers identify and mitigate vulnerabilities before release.
This guide summarizes key resources on functional programming, performance optimization, testing strategies, and coding standards, showing how mastering these four areas can transform any Python programmer into a highly effective and sought‑after developer.
This article explains how to combine MVP architecture with RxJava in Android development, covering framework selection, step‑by‑step MVP construction, thread management using RxJava, and practical Q&A on testing, modularization, and memory‑leak prevention, providing a comprehensive guide for building decoupled, responsive mobile apps.
This article clarifies common misunderstandings about agile development, explains why it can be faster than traditional methods by reducing pre‑development waste, early releases, and continuous testing, and offers practical illustrations through games, diagrams, and user‑story techniques.
The article examines how concise, efficient, and simple development practices—ranging from agile iteration and tool selection to testing automation and team management—can boost developer productivity, reduce waste, and enhance software quality across the entire software development lifecycle.
The article details the practical challenges, RTL rendering issues, Android version compatibility, string direction bugs, cultural content restrictions, numeral formatting, and testing procedures encountered while adding Arabic language support to a mobile application.
This article introduces Sikuli, an image‑recognition based UI automation tool, explains its advantages over traditional UI testing, details supported operating systems and required prerequisites, guides through installation steps, and demonstrates a simple Sikuli script for automating basic tasks.
Discover 26 practical agile development principles—from building test cases before code to avoiding premature optimization—that guide teams to deliver high-quality software efficiently, emphasizing incremental work, continuous testing, thoughtful design, and disciplined code management.
A collection of real‑world programming mishaps—from mixing test and production data to dangerous rm commands—illustrates why strict environment separation, cautious command execution, and disciplined code management are essential for reliable software operations.
This article describes how a product line can quickly establish a comprehensive, low‑cost automated CI/CD pipeline by first pinpointing shared development pain points, then creating a benchmark solution that can be replicated without additional expense, covering local builds, coverage metrics, performance testing, and automated online regression.
This guide walks developers through choosing a JavaScript framework, understanding ES6 and its variants, selecting appropriate build tools, and setting up effective testing workflows, offering practical recommendations and resources for both beginners and advanced front‑end engineers.
This article lists thirteen frequent production‑level problems—from missing configuration externalization and inadequate testing data to insufficient security, documentation, monitoring, and rollback planning—providing a checklist for developers and architects to prevent costly issues.
Badoo migrated its massive PHP codebase to PHP 7 across hundreds of servers, overcoming engine bugs, HHVM limitations, and extension incompatibilities, while revamping testing infrastructure and deployment processes, ultimately achieving up to 40% faster response times, eight‑fold memory reduction, and roughly one million dollars in cost savings.
This article explains Baidu's continuous integration (CI) journey, detailing the CI capability model, its three core factors—test coverage, build system, and team habits—along with metrics, scoring, and how the CI team supports product lines to improve development efficiency.
This comprehensive guide explains Python coding style best practices, covering PEP 8 extensions, flexible line length, naming conventions, docstring standards, functional versus object‑oriented design, testing, standard library usage, third‑party tools, and project structure to produce readable, maintainable code.
This article presents a detailed guide to modern Java development, covering coding style, immutable data structures, builder patterns, dependency injection, null handling, formatting, Javadoc, streams, publishing strategies, Maven configuration, CI tools, repository management, configuration automation, essential development tools, and a curated list of widely used Java libraries.
The article outlines the design principles, modular architecture, front‑back separation, lifecycle management, testing, and deployment strategies of Alibaba’s Detail platform, aiming to improve collaboration efficiency, stability, extensibility, and reuse across various business scenarios.
The article examines how Google maintains high code quality through rigorous code reviews, strict style guides, active code‑health initiatives, fix‑it events, and a strong testing culture, while also discussing the perception that older code inevitably degrades.
This article explains how to configure Android Studio for Robotium testing, create and run test cases, and integrate automated tests into a Gradle‑based continuous integration pipeline using Jenkins.
The article examines how concise, efficient, and simple development practices, agile iteration, automated testing, and thoughtful tool selection can boost individual and team productivity while maintaining software quality, offering practical examples and strategic guidance for optimizing software development processes.
Learn how to achieve comprehensive code coverage for multi‑process Node.js applications by using Istanbul, instrumenting child processes, writing Mocha tests, and merging coverage reports, with detailed examples of master‑worker RPC, custom fork hacks, and package.json scripts for automated testing.
The article outlines Baidu Cloud's comprehensive quality assurance framework—including testing technologies, specialized safeguards, and a multi‑stage QA evolution—demonstrating how data integrity, performance, and user experience are continuously measured, monitored, and improved for a cloud storage service serving hundreds of millions of users.
An in‑depth overview of KISSY, Alibaba’s home‑grown front‑end framework, covering its origins, architectural layers, modular system, component library, tooling, mobile support, testing, CI, and real‑world deployment examples such as shop and product detail pages, highlighting strengths and current challenges.
This article introduces six versatile Python libraries—Pyglet, Peewee, Bottle, Invoke, Splinter, and Arrow—that help developers quickly solve common tasks, from multimedia handling and database access to web APIs, automation, and date‑time processing, while remaining robust for larger projects.
This guide explains how to apply clean architecture principles to Android development by separating concerns into presentation, domain, and data layers, ensuring framework, UI, and database independence, and providing testing strategies and error‑handling techniques for a maintainable app.
This article details the evolution of Mobile Taobao's engineering architecture, development workflow, and quality assurance measures across three phases, illustrating how modularization, automated platforms, and rigorous testing practices enabled high‑quality continuous delivery for a large‑scale mobile application.
The article emphasizes that programmers achieve the software engineering iron triangle of cost, speed, and correctness by thoroughly understanding problems, crafting clear designs, listing test conditions, considering impacts on other components, and anticipating future issues, urging a slower, long‑term perspective before diving into code.
This article explains why H5 performance matters, defines the one‑second rule for different network conditions, and provides comprehensive front‑end optimization techniques—including resource loading, image handling, server deployment, code standards, testing tools, and classic case studies—to improve user experience on mobile web applications.
Over the past two months I helped develop a distributed hybrid‑cloud platform, tackling challenges from OS differences and network ports to message queues, logging, multi‑language integration, and testing, and I share the architectural decisions, tooling choices, and practical lessons learned for building robust backend systems.
This guide explains how to use Redis's built‑in redis-benchmark tool to measure the throughput of local or remote Redis instances, covering basic testing, selective command benchmarking, and remote server testing with practical command examples.
This article provides an extensive overview of modern JavaScript development, covering the transition to ES2015, module systems, build tools like Webpack, testing frameworks, process automation, code quality tools, Git workflows, client‑side templating, and essential Node.js knowledge for frontend engineers.
The article outlines thirteen critical production‑related mistakes—from not externalizing configuration and using inadequate test data to neglecting security, documentation, disaster‑recovery planning, and proper capacity planning—providing actionable guidance for developers and architects to improve system stability and performance.
The article explains how over‑complex mental models, poor translation of semantic ideas into code, inadequate naming, missing design chunks, unclear usage patterns, and lack of smooth model transitions cause code to decay, and offers practical principles such as DDD, SRP, good naming, testing, and reusing existing algorithms to maintain readability.
A recent study of five major open‑source distributed systems reveals that most failures can be triggered and reproduced with simple, multi‑event tests, highlighting the importance of systematic testing, deterministic error handling, and concise logging for reliable system operation.
The article provides a detailed, data‑driven look at Google’s internal software development practices, covering unified trunk code management, pervasive code visibility, rigorous reviews, feature‑flag experimentation, strict testing, and the blend of Java, C++, and JavaScript in front‑end and back‑end work.
When inheriting tangled legacy code, first decide if you’re responsible and willing to invest, then establish comprehensive tests, use version control, make incremental changes, separate cleaning from bug fixing, remove dead code and comments, avoid mutable shared state, and eliminate unnecessary complexity to improve maintainability.
