It seems it is about the time to share the list of my "favorite" bad practices:
- Sporadic bugs are ignored. This compromises user experience and test automation.
- Performance issues are ignored as sporadic. This leads to performance degradation over time.
- Test environment does not match Live environment - "It is too expensive". This compromises test automation scalability and performance testing.
- When problems(not clear bugs) are reported by QAs they are ignored. If latter the same are spotted by client or manager everyone are starting to work on them.
- There are no set dates for the development to complete the features, but release dates for the product are set. So Testing is expected to be "elastic".
- Automated tests are blamed to be slow while actually application is slow.
- UI changes are done without consideration that this will impact automated tests.
- Critical and blocking bugs does not reset testing cycle at all.
- There is no stable release branch for QA to test. QAs are forced to test on master branch where tens of commits are done every day.
- Test blocking problems are not fixed for days.
- QAs are overloaded with many parallel releases.
- QAs evaluation(salaries, bonuses, promotions) are in the hands of development manager. Guess what is the result of this.
- Management cares only for the release dates, but is not interested in quality. The quality for them is like religion. (If interested on this topic read Rex Black)
- Management improves development process by transferring more manual work to QAs - for example automatically putting stories and bugs to ready status without they are actually ready for test
No comments:
Post a Comment