Regression Testing

When doing regression testing its good to know what your ressesing. For instance if your testing an enhancement then you'll need to be updating the test suite for changes. If you testing for bug fix then the test may have already covered this and thus has a fail for it. If you testing to full fill quartler audits then automation is the way to go.

When code breaks, keep breaking it...

Nothing more fun than getting a new build with fixes that have regessed old issues, created new issues or have not address an issue, though code had been added or changed.

Most Software Stinks! and beyond

http://www.chc-3.com/pub/beautifulsoftware.htm

http://www.developer.com/tech/article.php/923751

Navajo Tradition of development

When there is no documentation either via comments or business requirement documentation or flow chart, when all you have are the words of your predecessor and maybe some instruction on how they performed the functions of their job.

Unit testing: When dev smokes in the sandbox QA cleans up the butts

Knowing that the code works and what to do if it don't.

Where is it running; local, prod, sandbox?
In the Sandbox where is it stopping; echo statements, database connections?
What do the logs say? Log, Log its better than bad its good.
Does an error write; to the screen, view source, URL?
Does the code meet the stakeholders expected results?

If so then so do so

else write a bug.