Greg LeMond Quotes

A program that has not been tested does not work.

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

I used Agitator on some code I had unit-tested, and it made me a better tester. As an Agitar Fellow, I look forward to the leverage of working with an outstanding organization as together we continue to improve the value of developer testing.

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

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

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

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.

You don't want to come out with anything that's wrong, of course, in a scientific, you know, a major scientific announcement, and so you're being so careful trying to check, well maybe it's this, maybe it's that, you're looking at every possible thing.

Agitator and the Agitar Management Dashboard lower the barriers to accountability in software development and increase the value of developer testing.

I found out that most programmers don't like to test their software as intensely as I do.

I just think if you're going to do something, do it properly.

No one would say, 'Hey, I think this medicine works, go ahead and use it.' We have testing, we go to the lab, we try it again, we have refinement. But you know what we do on the last mile? 'Oh, this is a good idea. People will like this. Let's put it out there.'

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

Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce.

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.

No trusting without testing

I would ruin my credibility if I put my stamp of approval of anything I didn't do my due diligence on.

Everything is a test.

Across th street is a hell of a tester.

Do I pass, Dr. Saunders?

If I set off to do something, why not do it properly? Otherwise, what's the point?

I'm uncommonly slow to show my work to other people, and by the time I do I've usually exhausted myself so completely that all I really want is for someone to tell me that my efforts have added up to something - not one of my better qualities, I admit.

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.

Whatever you do big or small, do it well or don't do it at all.

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.