Michael Bolton Quotes

Running the test suite like this allows us to catch problems when they are just introduced.

One of the headaches of high-tech test programmes is having to debug the test arrangements before you can start debugging the things you're trying to test.

Testing is overrated.

Today, we can tell people we have a testing process and facilities in place on a nationwide basis.

We have a very active testing community which people don't often think about when you have open source.

I'm not saying we purposely introduced bugs or anything, but this is kind of a natural result of any complexities of software... that you can't fully test it.

Testing can be used to show the presence of bugs, but never to show their absence!

As you get to the end of the project you want to run all the tests cases against one version and make sure that you know that that version passed everything. And so as you get late in the project you get a little more conservative about making radical changes to the software.

Testing shows the presence, not the absence of bugs.

When you develop software, the people who write the software, the developers are the key group but the testers also play an absolutely critical role. They're the ones who ah, write thousands and thousands of examples and make sure that it's going to work on all the different computers and printers and the different amounts of memory or networks that the software'11 be used in. That's a very hard job.

The real value of tests is not that they detect bugs in the code but that they detect inadequacies in the methods, concentration, and skills of those who design and produce the code.

All real programs contain errors until proved otherwise which is impossible.

A program that has not been tested does not work.

If I say I've got two versions of Word - that old one from 1982 that's perfect, with zero defects; or the new one that's got all this cool new stuff, but there might be a few bugs in it - people always want the new one. But I wouldn't want them to operate a plane I was on with software that happened to be the latest greatest release!

I think it's a combination of technical and social factors that leads to all the defects in deployed software.

When I write software, I know that it will fail, either due to my own mistake, or due to some other cause.

As a rule, software systems do not work well until they have been used, and have failed repeatedly, in real applications.

Well, user feedback was excellent. Even when the software didn't work at all, there were few people who were avid users, and there were people who were just sending excellent feedback and excellent ideas.

Writing software that's safe even in the presence of bugs makes the challenge even more interesting.

I'm not a programmer myself, but I am a very, very picky end user of technology. I like my machines to work they way they're supposed to, all the time.

Software development is technical activity conducted by human beings.

Like any well designed software product, Windows is designed, developed and tested as an integrated whole.

A very important part of game development is testing - something that a lot of developers don't do.

In software engineering, we have the term 'technical debt.' When you don't do a job correctly, unaddressed problems become harder and harder to solve.

It's important not only to have the right timing of when the hardware is going to be released but also when we are going to be able to introduce quality software.