The GUI changes. The script fails because the GUI changed. Manual testing shows that the GUI does what it is supposed to do.
A database access script changes and introduces a side effect that breaks a script.
The scripts need to be fixed but are not, due to time limitations and staff availability.
There can be issues with QA staff skills. Some staff are good with the application being tested, but are weak with scripting, so they misinterpret Log error messages and misreport the results.
So far two people have responded that they keep everything in the TC Log system and do not break it out because they do not see a need to.
