Smarter Test Engineering

I was reading a post "5 Things I hate in testing"
(http://www.softwaretestingclub.com/forum/topics/5-things-you-hate-about and below are the common things that I liked from that post:

1. Crappy, unreliable test environments where most of my time and effort is expended identifying environment issues rather than product issues.
2. Code that isn't architected in a testable manner, causing testers to have to write integration tests when simple unit tests could find the same bugs.
3. Testers who get comfortable with what they already know and stop pushing themselves to learn more.
4. Unproductive test-tool, which was historically over-purchased and still, swallows a recurring chunk of budget.
5. The lack of standard education around the field.
6. Management focus on numbers (without considering context)
7. The perception that a career in testing is somehow of less value
8. Testers doing some manual mundane tasks repeatedly, where technology can be applied and used. (For example preparing a 1 GB file manually or typing 255 characters). We are solving the problems in Technology and we are not using Technology to solve our problems.
9. Testing team not informed about the changes.

In this post I came across many things that testers hate in testing.

For point # 5 mentioned above, one solution can be introducing “Software Testing” as a Subject (both theory and practical) in all professional courses. Many Students don’t know what Testing is until they join some training institute or forced to do a testers role.

For point # 8 mentioned above, one solution can be using tools like http://www.testersdesk.com/ or scripting some programs to reduce our effort. For example if you need to check the files installed in some part of your system you can write a small vbscript to see the folder structure and its contents by just inputting the path.

My dear readers please give your solutions to avoid the above listed things.

Happy Testing,
Bhagawati