Are you working with a big testing team? Is your test team understaffed? If not it will be soon understaffed. Your teammates work on different modules of the product.If you feel you are working alone then you may call yourself an Omega Tester.
Omega Tester generally faces the following issues.
Anything you do means something else won't get done: You cannot be a multi tasker. If you start your work then you will put on hold other tasks like communicating with others, preparing, learning ..etc. You are a single-threaded person.
You feel too busy to plan and prepare: You may need to read functional specifications, discuss with developers, use tools and setup testing environments. You need to understand the product and imagine the risks to prepare test strategy. On top of which you also need to attend a lot of meetings. Finally, the pressure is on you. A small amount of development can create a lot of work for testers. For example, a modern web application bug fix need to be tested on all affected areas, on all supported browsers, and if the web application supports different themes then you have to test on all themes too. Developers create new functionality and testers need to catch up with them. They also introduce performance problems, scalability problems and usability problems..etc for free. You cannot find these problems for free.
You feel too busy to mind your infrastructure: You need to stop testing and organize your test data, update coverage, and risks list when your desktop is full of notes and files. A good infrastructure for your test project gives you efficiency, but you may feel that efficiency is a luxury you can't afford
You feel too busy for curiosity: Testing is like a search. There is no optimal way to find bugs. Excellent testing requires that you test more than the obvious things in the obvious ways. You must indulge your curiosity. You must play. You must open yourself to the unexpected. For many testers, this can be hard to justify It looks like you are going off the track, instead of doing important work. So, when the pressure is on, curiosity is easy to put on the shelf. You then become a little more like a fancy robot; a little less like a powerful human tester
Omega Tester generally faces the following issues.
Anything you do means something else won't get done: You cannot be a multi tasker. If you start your work then you will put on hold other tasks like communicating with others, preparing, learning ..etc. You are a single-threaded person.
You feel too busy to plan and prepare: You may need to read functional specifications, discuss with developers, use tools and setup testing environments. You need to understand the product and imagine the risks to prepare test strategy. On top of which you also need to attend a lot of meetings. Finally, the pressure is on you. A small amount of development can create a lot of work for testers. For example, a modern web application bug fix need to be tested on all affected areas, on all supported browsers, and if the web application supports different themes then you have to test on all themes too. Developers create new functionality and testers need to catch up with them. They also introduce performance problems, scalability problems and usability problems..etc for free. You cannot find these problems for free.
You feel too busy to mind your infrastructure: You need to stop testing and organize your test data, update coverage, and risks list when your desktop is full of notes and files. A good infrastructure for your test project gives you efficiency, but you may feel that efficiency is a luxury you can't afford
You feel too busy for curiosity: Testing is like a search. There is no optimal way to find bugs. Excellent testing requires that you test more than the obvious things in the obvious ways. You must indulge your curiosity. You must play. You must open yourself to the unexpected. For many testers, this can be hard to justify It looks like you are going off the track, instead of doing important work. So, when the pressure is on, curiosity is easy to put on the shelf. You then become a little more like a fancy robot; a little less like a powerful human tester
No one understands what you do: Programmers and testers both do work that is intangible. The difference is that programmers have a tangible finale: the software. The end product of testing is less tangible, and efforts to make it more tangible means spending less time on actually testing. Many people think testing is easy and they wonder why it takes you so long to find those "obvious" bugs. At least if you are in a team of testers, you can commiserate and share the burden of explaining the impossibility of complete testing for the 37th time. As an omega tester, you just feel surrounded by monsters.
No comments:
Post a Comment