Quotessence
Home / Topics / Software Testing Quotes

Software Testing Quotes

Browse 16 quotes about Software Testing.

Software Testing Quotes

“Most literature on the subject of agile methodology... is written from the viewpoint of software developers and programmers, and tends to place its main emphasis on programming techniques and agile project management—testing is usually only mentioned in the guise of unit testing and its associated tools. ...However, unit tests alone are not sufficient and broader-based testing is critical to the success of agile development processes.”

“I write them to improve my productivity as a programmer. Making the quality assurance department happy is just a side effect. Unit tests are highly localized. Each test class works within a single package. It tests the interfaces to other packages, but beyond that it assumes the rest just works. Functional tests are a different animal. They are written to ensure the software as a whole works. They provide quality assurance to the customer and don't care about programmer productivity. They should be developed by a different team, one who delights in finding bugs.”

“Tests are sometimes mistaken with quality assurance. These two notions are not identical: 1) quality assurance ensures that the organization's processes are implemented and applied correctly; 2) testing identifies defects and failures, and provides information on the software and the risks associated with their release to the market”

“When the automation test pack is being designed, the most important decision is to plan the Test Scheduling of those Automated Test Scripts. The objective of test automation is to reduce the amount of time spent in Regression Testing”

“The simplest answer is that the user had access to reality—every company builds a bubble around itself, where the products get built and tested in a more controlled environment than they get used in. This is especially true of complex software. What the early users enabled Xiaomi to see was how MIUI actually worked when real (albeit unusually technically proficient) people tried to install it on a wide variety of devices.”

“Some people mistakenly refer to software defects as bugs. When called bugs, they seem like pesky things that should be swatted or even ignored. This trivializes a critical problem and fosters a wrong attitude. Thus, when an engineer says there are only a few bugs left in a program, the reaction is one of relief. *Supposed, however, that we called them time bombs instead of bugs.* Would you feel the same sense of relief if a programmer told you that he had thoroughly tested a program and there were only a few time bombs left in it? Just using a different term changes your attitude entirely.”

“The approach shown... is a common pattern for testing exception-throwing behavior with JUnit. @Test public void missingValueRaisesException() throws Exception { try { new Template("${foo}").evaluate(); fail("evaluate() should throw an exception if " + "a variable was left without a value!"); } catch (MissingValueException expected) { } }”