You've got to trust a company whose motto is "If it's not tested, it doesn't work." This motto was created in the fires of our early years as engineers. How many times did we make just that one little change and say: "Oh, it's obvious that this will work." Then when we test it, we find, that to our surprise, it could never have worked.

Testing, testing and more testing. Testing by individuals other than the designers. Testing by individuals most like the end users. Why do we designers hate to find problems with our own stuff? The same designer who brings terror to the heart of our developers whenever he is asked to test their work, acts completely different when testing his own code.

Another key principle for us is to test to a written test plan. Like other phases of documentation, many companies talk about it but don't do it. Again the balance of crossing every "t" and dotting every "i." We have come up with a very efficient and workable technique for generating and executing our test plans.

Occasionally, MicroTools is called in to test software and/or systems that we had no role in developing. Under those circumstances, we develop a test plan, execute it, and then hide for cover from the developer's wrath. If you are a manager, try us, you'll like us. If you are a developer, skip to the next page.

Click here to read more about our fixed price testing