Third Issue: QA Roles, Delivery Quality Evaluation, Distributed Locks, Defensive Coding, and iOS Stability Testing

Third Issue

1. What can QA do in a “de‑QA” project?

Discusses the shift towards “de‑QA” and encourages QA professionals to find new ways to add value by improving quality and efficiency beyond traditional testing.

2. How to evaluate team delivery quality

Outlines three dimensions—process quality, result quality, and non‑business attributes—detailing metrics such as requirement completeness, build success rate, defect trends, delivery time, online defect rate, user feedback, data tracking, maintainability, and scalability.

3. Concurrency – Distributed lock quality assurance summary

Explains the importance of quality assurance in high‑concurrency e‑commerce scenarios, using distributed locks as a basis to introduce testing methods for concurrent systems.

4. How to practice “defensive coding”

Highlights that defensive coding is a shared responsibility of developers and testers, offering examples of handling exceptional cases during design, test case creation, and code review.

5. iOS stability testing practice at iQIYI

Describes iQIYI’s self‑developed solution for long‑duration iOS app stability testing, including tools like FastMonkey and methods for detecting crashes, memory leaks, and performance degradation.