Уровень 0 · материалов: 8
В кластер входят документы, описывающие теоретические подходы, принципы и организационные процессы тестирования программного обеспечения, и не входят документы, посвященные конкретным инструментам или техническим инструкциям по тестированию.
Общие признаки: цели и задачи тестирования, процессы обеспечения качества, роль тестировщика в разработке, различие между QA и QC
Группа выше: Методология и терминология тестирования
Смысл: The main idea is that professional software testing should be a risk-management process focused on ensuring critical functionality for the user, rather than a quantitative game of finding as many defects as possible.
True software testing focuses on preventing the leakage of critical defects to the user through strategic analysis and user-centricity, rather than simply maximizing the number of reported bugs.
Смысл: The main idea is that software testing is not merely the act of finding bugs, but a structured process of verifying a product's compliance with direct and indirect requirements to provide stakeholders with accurate information about the product's state.
An experienced QA manager explains the theoretical foundations and specific answers he seeks during interviews to distinguish true testing professionals from superficial 'button-clickers'.
Смысл: The main idea is that software testing is fundamentally a process of providing negative feedback to improve a product. It is a disciplined activity of creating artificial situations to verify that a program's actual behavior matches its expected requirements.
Software testing is the practice of providing negative feedback on product quality by observing program behavior in artificial situations to ensure compliance with requirements.
Смысл: The main idea is that software testing should be integrated into the engineering culture as a means to increase development speed and productivity, rather than being a standalone quality-control gate. It advocates for a shared responsibility of quality, tiered automation, and the prioritization of real-world user feedback over simulated testing.
Google views testing as an integral part of engineering productivity, utilizing specialized roles (SWE, SET, TE), tiered automation, and rapid user-feedback loops to accelerate development without sacrificing quality.
Смысл: The main idea is that professional game testing is a structured process reliant on standardized documentation to ensure product quality and efficient communication between developers and testers.
A detailed overview of the critical documentation artifacts and requirements analysis processes necessary for a professional Game QA Engineer.
Смысл: The main idea is that quality should be the responsibility of the creator (the developer) rather than a separate entity (the tester), and that traditional manual testing should be replaced by shared team responsibilities and high-level professional quality assurance.
Quality assurance should be a shared team responsibility and a culture of development rather than a separate phase of manual bug-hunting.
Смысл: The main idea is that the principles of system reliability and failure analysis from aerospace engineering are directly applicable to software development: prioritize intuitive interfaces, encourage comprehensive bug reporting, and replace error-prone manual processes with automation.
Using Soviet space mission failures as case studies, the author explains why developers should focus on UX, encourage bug reporting, and prioritize automation over manual effort.
Смысл: The main idea is that QA and Testing (QC) are fundamentally different disciplines: one is about preventing defects through process improvement, while the other is about detecting defects in the final product. The author advocates for a shift in mindset from reactive testing to proactive quality assurance to create better products more efficiently.
The article clarifies that while 'QA' and 'tester' are often used interchangeably in job postings, QA focuses on preventing bugs early in the process, whereas testing (QC) focuses on finding them at the end.