Miguel de Icaza Quotes

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.

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

A program that has not been tested does not work.

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

Testing, we will never do enough of it.

An individual developer like me cares about writing the new code and making it as interesting and efficient as possible. But very few people want to do the testing.

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

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

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.

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.

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

Beware of bugs in the above code; I have only proved it correct, not tried it.

One of the advantages of having to live with JUnit for 8 years is now we can look back and see which decisions we made worked nicely and which we would have done differently.

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.

But typically for a project like the Mac, the size we had was pretty good. And it has different stages. The team grows as you have to write manuals and do testing... though the Mac had no formal testing.

The process of software development doesn't feel any better than it did a generation ago.

There is a strong movement towards increased accountability for software developers and software development organizations.

This will surprise some of your readers, but my primary interest is not with computer security. I am primarily interested in writing software that works as intended.

There are two ways to write error-free programs; only the third one works.

There has never been an unexpectedly short debugging period in the history of computers.