Software Quality Assurance

Junit, Nunit, xUnit....So unit testing is importing. And the most important at the start of the development life cycle. Its no surprise to anyone in Test or QA that running testing scripts and having a test plane and unit tests ready for programmers and developers to review before coding begins is going to reduce bugs but how do you get your business to understand this?

What it means to change produciton server location. New hardware same applications what should be updated. What applications get cut over first. New hardware.... Same code base... Sync content w/ test and prod The cut over to a new data center

Complex system have inherent flaws or exploits that are often unintended side effects many things, the defined requirements, the developers time and resource constants

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.

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.

http://www.chc-3.com/pub/beautifulsoftware.htm http://www.developer.com/tech/article.php/923751