Tag Info

Hot answers tagged

13

Welcome to SQA, user5440. "High level software QA" could refer to a architect-level position, or a management position, or something else; maybe even a job testing zeppelin software, or testing marijuana distribution software in California. Or it might mean ordinary testing from the perspective of someone who doesn't know anything about software, or who ...


6

Robust is the opposite of fragile; it is the ability to function correctly under a variety of conditions -- perhaps even under conditions that change or that you did not anticipate. Robustness testing is the practice of measuring robustness. Fault injection and mutation testing are ways to measure the robustness of your tests. They don't tell you anything ...


2

Pesticide Paradox The phenomenon that the more you test software, the more immune it becomes to your tests - just as insects eventually build up resistance and the pesticide no longer works. [Beizer] from: http://www.allthingsquality.com/p/testing-terms-glossary.html


2

How about fast failing vs fault tolerant? A fast failing system will frequently check for failures and fail when encountering them. A fault tolerant system will experience them but continue to operate with a possible degradation in performance. Struggline with misbehaviors as you've described it. http://en.wikipedia.org/wiki/Fail-fast ...


1

Historically Quality Control is term from 1970s which meaning was controlling of the final product quality. In 1980s this term get a new meaning when people realized that they should also control quality of intermediate products. A decade later term Software Quality Assurance came up when stress was set not only on quality of products but also on ...


1

I see this in Ian Somerville's book (9th edition, section 8.3): There are two important distinctions between release testing and system testing during the development process: A separate team that has not been involved in the system development should be responsible for release testing. System testing by the development team should focus on ...


1

I have always called this Acceptance Testing, it doesn't matter who the Customer is running it (at least in my world, yours will differ) so long as it has a set of Agreed upon tests to run that can be said to "Accept the release to production". Standards in Software depends on what general set of standards you follow, but mostly it's a "depends" answer, ...


1

Boris Beizer wrote “Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffectual.” In the most simple terms not every method or technique will find or prevent all bugs, so we must use a variety of approaches, techniques, and methods in testing. See this post for more info



Only top voted, non community-wiki answers of a minimum length are eligible