Despite giving the company four stars, there are still some cons, some small and some rather bothersome.
1. There isn't much room for growth. Every now and then a supervisor position will open up, but to me they liked to choose favorites rather than the person that deserved it. If you are a tester and don't have any programming skills, you will be stuck making $12 an hour with no raises or anything aside from quarterly bonuses. There are people that have worked there for5 or 6 years that still make $12. The best mobile tester there makes the same amount as the worst tester there and that's just wrong imo.
2. Management. Your direct supervisors are right there with you and understand how it is on the floor which is good, however the upper management is pretty out of the loop on how things work and don't really try to understand it from a testers point of view. Employee feedback is thrown out the window and seen as complaining rather than valid concerns.
3. Employee treatment and feedback. Every concern a tester throws out is seen as a complaint and shot down every time even though the concerns are valid and would actually help the company. For example, as testers we have to test everything based on what the test case writers write. Towards the end almost 80% of test cases written were incorrect and needing editing. Various testers brought this issue up because it made our jobs harder and every time it was shot down. The reason this is a real issue is because testing needs to be accurate, so when a test case is written incorrectly, its tested incorrectly. Often times, testers or even sups won't know if a test case is incorrect so we would have to search for the ticket saying if its correct or not. That usually took around 20 minutes, just for one test case block. Now 20 minutes may not seem like a long time but when its 80% of the test cases you are searching for tickets more than actually testing. Not only that but for every wrong test case, the tester has to write a test case edit in a separate sheet, but the edits are never checked and never edited. There were test edits that were sitting in there for a year and a half and never edited on the testing sheet, meaning those test cases were wrong for over a year and each time we would have to put in an edit, so there were sometimes 50 plus of the same test edits that never got resolved. That's not efficient at all. Test case writers are also supposed to put the corresponding ticket next to the test case blocks and that never happened. Sometimes test cases were written by obviously outdated tickets, but it was like the test case writers didnt care or their manager didn't care. So knowing all that, its easy to make a mistake when testing and when there is a mistake, the testers are the ones that take the blame no matter what. It almost felt like the test case writers weren't held to the same standards the testers were. That's a huge con imo. Efficiency isn't very good there.
