Transitioning to one project from multiple projects.
A while ago, I shifted to a single project team. This team is working with a Silicon Valley startup and helping them in some areas. My job is to test their Android app.
The past year I have been working as the sole tester for a few small teams each working on a few different projects. There were different projects with different platforms and different sets of requirements and functionalities. It is all very colorful getting your hands dirty with anything and everything you can.
It has been 3 months since I have been with this (single) project. It’s really cool working with the new team and the Bay Area people are especially very nice. Not to mention, there is an awesomeness associated with it only because it’s a Silicon Valley startup.
While a lot of good came from working on this project, I liked working on multiple projects simultaneously better. Here is everything I learned, enjoyed and miss about it:
Little bit of everything
When I was starting out as a QA Engineer, working on different projects turned out to be very beneficial in terms of developing my testing skills. I got to taste everything. I started with a web app’s functionality testing, then I got to test the web and mobile version of another app, then I got to test another mobile app. I learned functionality testing, UI testing and after some time I was even assigned a security testing task which provided me very interesting insight into penetration testing
Bonus: Here is something I wrote about it:
Security Testing – OWASP ZAP: A review
Furthermore, I got to try out Selenium IDE which I didn’t like very much so I experimented on Selenium WebDriver and found it very powerful. Later I learned a great deal of Apache Jmeter for API Testing of a very comprehensive web app.
I got to learn about different types of testing, test management, time management, the importance of communication and the list goes on. One advantage of this is that since you encounter so many different types of systems, apps, platforms, tools and testing,you can pick a favorite and specialize in that area.
It is hardly ever a dull day. I was usually working on at least two projects at a time and I never get bored. The diversity always kept me going. No matter how big an app you’re testing, there comes a point when you get tired of looking at the same UI and the same features. In that case, you don’t have to look for anything outside of your work to feel refreshed again.
Having to work on multiple projects at a time isn’t always enjoyable if you have a lot to cover. There is a limited time, there is a deploy planned and you have to make sure that everything works well. You have to fit in a lot in a small time. On the bright side, you come out of it all as a person with better time management skills.
Focusing solely on one project brings a certain monotony to your life, from what I have observed. But there are good and boring parts to all sorts of work. To me, reading is the absolute monotony killer. Also, I enjoy learning something new whenever time allows me. It all depends on how you choose to love and enjoy your work despite everything.