1 views collected around this technical thread.
This article provides a comprehensive tutorial on Monkey testing for Android applications, covering the complete workflow from environment setup to test execution, monitoring, and analysis.
This article introduces Monkey testing on Android, explaining its purpose, key characteristics, and how to set up the environment and run basic tests using ADB commands to improve app stability and automate stress testing.
This article provides a comprehensive overview of performance testing fundamentals, covering key concepts, common test types, popular tools, test design strategies, defect management, special‑scenario testing, advanced topics like APM and micro‑services, best practices, and future trends in the field.
This article provides a comprehensive overview of performance testing fundamentals, covering core concepts, key metrics, common testing tools, test design, load generation, result analysis, bottleneck identification, optimization techniques, cloud and micro‑service testing, monitoring, reporting, challenges, and cost‑benefit considerations.
This article describes a comprehensive approach to stress‑testing a WebRTC SFU service with 300 concurrent connections, covering client generation via Playwright, monitoring setup, test execution, encountered issues, tuning steps, and final performance conclusions.
This article outlines the end‑to‑end design of a high‑availability flash‑sale system, covering traffic spikes, overload protection, inventory consistency, multi‑level caching, token‑bucket rate limiting, distributed queue processing, service monitoring, and stress‑testing strategies to ensure reliable million‑level transaction handling.
This article explains why performance stress testing is essential, describes core metrics and the wrk tool, outlines a step‑by‑step testing workflow, analyzes bottlenecks, and presents concrete optimization measures that doubled the single‑machine QPS from 300 to 600 for a Nuxt‑based web service.
This article introduces a variety of Linux command‑line tools used for stress testing and performance monitoring, covering CPU, memory, disk, network, processes, load, temperature and other utilities with brief usage examples and practical tips.
This article introduces a collection of essential Linux command‑line tools for stress testing and monitoring system resources such as CPU, memory, disk, network, processes, load, temperature, and other aspects, helping administrators assess stability and performance.
This article presents a systematic method for evaluating and prioritizing stress‑test coverage in game projects, combining comprehensive “addition” techniques—such as QA requirement gathering, case‑library reference, test‑case review, and server‑architecture analysis—with precise “subtraction” methods to refine the final test set.
DeWu’s tech team describes how their e‑commerce platform grew from a simple PHP monolith to a containerized active‑active, multi‑region system with hot‑standby failover, comprehensive governance, full‑link stress testing, and detailed big‑sale preparation, illustrating a systematic, evolving high‑availability architecture that balances scalability, disaster recovery, and business continuity.
This article explains the purpose, sources, and manifestations of pressure in Alluxio, describes its built‑in stress testing framework, outlines how to run and configure stress tools, and provides guidance on result calculation, reporting, common issues, and debugging for effective performance evaluation.
This article explains what performance testing is, when to conduct it, typical scenarios, step‑by‑step execution—including requirements, test design, tool selection, script examples with Locust, result analysis, and key metrics such as throughput, response time, P90, and optimal concurrency.
The report details JD International Technology R&D’s first comprehensive preparation for the 2022 618 sales event, describing multi‑regional challenges, the establishment of rapid response mechanisms, stress‑testing activities, operational highlights, identified shortcomings, and actionable recommendations for future large‑scale promotions.
Bilibili’s senior test engineer Lu Kai built a platformized live broadcast stress‑testing system with five modules—metadata collection, task configuration, pressure generation, performance data collection, and reporting—that reuses thousands of cases, simulates high‑QPS traffic, detects hundreds of bugs and memory leaks, and improves iOS and Android app performance for major events.
To deliver a flawless live broadcast of the 2021 League of Legends S11 World Championship to over 100 million viewers, Bilibili mobilized hundreds of engineers for four months, establishing strict standards, modeling dozens of user scenarios, estimating traffic, conducting layered stress and chaos tests, implementing automated and manual degradation, detailed SOPs, rate‑limiting safeguards, and on‑site monitoring, which together ensured system stability throughout the event.
This article details a practical reproduction of a large‑scale WeChat red‑packet service, describing the design goals, hardware and software setup, concurrency architecture, monitoring tools, and performance results that demonstrate a single‑machine handling one million connections and up to sixty thousand queries per second.
This article provides a comprehensive guide to game pressure testing, covering the full workflow from requirement communication and test planning to execution, performance analysis using tools like LuaProfiler, Perf, and VTune, and detailed result interpretation with case studies.
This article explains the theory and practice of game stress testing, covering four test types (server, client, third‑party services, cloud gaming), key performance indicators such as CPU, memory, network and log metrics, and the use of server and client robots to simulate real‑world load.
This article explains how to perform MySQL performance benchmarking with the built‑in mysqlslap tool and the third‑party sysbench utility, covering configuration changes, command‑line options, data preparation, execution steps, and interpretation of the resulting metrics.