Quotes About Testing

delayed because of external commitments made to Wall Street or customers. Then you add a bunch of developers who use up all the time in the schedule, leaving no time for testing or operations deployment. And because no one is willing to slip the deployment date, everyone after Development has to take outrageous and unacceptable shortcuts to hit the date.

Testing is done in scarce integration test environments, which often require weeks to obtain and configure. The

Because our goal is to enable small teams of developers to independently develop, test, and deploy value to customers quickly and reliably, this is where we want our constraint to be. High performers, regardless of whether an engineer is in Development, QA, Ops, or Infosec, state that their goal is to help maximize developer productivity.

Without automated testing, the more code we write, the more money it takes for us to test.

a small number of reliable, automated tests are almost always preferable over a large number of manual or unreliable automated tests.

When John agrees, I thank him for his time. "Wait, one more question. Why do you believe that this product didn't cause the failure? Did you test the change?" There's a short silence on the phone before John replies, "No, we couldn't test the change. There's no test environment. Apparently, you guys requested a budget years ago, but…" I should have known.

The plot is simple: First, you take an urgent date-driven project, where the shipment date cannot be delayed because of external commitments made to Wall Street or customers. Then you add a bunch of developers who use up all the time in the schedule, leaving no time for testing or operations deployment. And because no one is willing to slip the deployment date, everyone after Development has to take outrageous and unacceptable shortcuts to hit the date.

Great QA requires a perverse and sometimes sadistic intuition for what will cause software to blow up, crash, or endlessly hang. Maxine once heard a joke: "A QA engineer walks into a bar. Orders a beer. Orders zero beers. Orders 999,999,999 beers. Orders a lizard. Orders negative one beer. Orders a 'sfdeljknesv.

every Facebook user was part of a massive load testing program, which

We all know we need to change how QA does testing, but the best place to start is by changing how Dev does testing.

This includes the creation of automated build, integration, and test processes so that we can immediately detect when a change has been introduced that takes us out of a correctly functioning and deployable state.

Automated testing helps developers discover their mistakes quickly (usually within minutes), which enables faster fixes as well as genuine learning-learning that is impossible when mistakes are discovered six months later during integration testing, when memories and the link between cause and effect have long faded. Instead of accruing technical debt, problems are fixed as they are found, mobilizing the entire organization if needed, because global goals outweigh local goals.

We cannot achieve deployments on demand if every code deployment requires two weeks to set up our test environments and data sets, and another four weeks to manually execute all our regression tests. The countermeasure is to automate our tests so we can execute deployments safely and to parallelize them so the test rate can keep up with our code development rate.

the developers will eventually be responsible for testing their own code, with QA taking a more strategic role, coaching and consulting.

Humble and Farley define the difference between unit and acceptance testing as, "The aim of a unit test is to show that a single part of the application does what the programmer intends it to....The objective of acceptance tests is to prove that our application does what the customer meant it to, not that it works the way its programmers think it should.

Instead of merely documenting the specifications of the production environment in a document or on a wiki page, we create a common build mechanism that creates all of our environments, such as for development, test, and production. By doing this, anyone can get production-like environments in minutes, without opening up a ticket, let alone having to wait week.s

Whether we like the idea or not, war has again and again been seen as the great auditor, the special testing time, of a nation's strength and fibre.

This talk of love means very little. Love is not a feeling. It can be tested. Love is action, it is silence. It's not the emotional straining and scheming for possession that you used to think it was.

The theory of universal gravitation is not cast-iron. No theory is, and there is always room for improvement. Isn't that so? Science is constructed out of approximations that gradually approach the truth. . . Well, that means all theories are subject to constant testing and modification, doesn't it? And if it eventually turns out that they're not quite close enough to the truth, they need to be replaced by something that's closer. Right?

Science doesn't purvey absolute truth. Science is a mechanism. It's a way of trying to improve your knowledge of nature. It's a system for testing your thoughts against the universe and seeing whether they match.

We've done a zombie episode - only one - and the way we look at it as is we understand that there probably aren't zombies out there for real, but there's a lot of interesting stuff we can test about them. We've tested how bodies of zombies pressing against a gate, would they push it through and things like that.

Some are happy with where their comfort zone is, but I like to be constantly tested, and I think it's good.

It is all well and good talking about it, but until you get tested and come out of your comfort zone a bit, you don't see how you really are as a player.

God tests His real friends more severely than the lukewarm ones.