Every January, many of us make their New Year's resolutions as to what we want to achieve in the next 12 months. Be it personal growth or career, we all want to improve different fields of our lives.As Apptension’s QA team, we’ve decided to start a list of our own.For all QA teams out there - this could be a great exercise for you as well, as it helps you analyze what it is that you need to focus on the most in terms of learning and improvement.For example, exactly one year ago, we didn’t have a lot of experience with testing automation. Our CEO, Zbigniew, encouraged us to develop our automation skills and make it the QA team’s 2016 goal.We did focus on that and the effects are clearly visible - our tests are finding the bugs for us, woo hoo! Quite honestly, we can’t imagine our projects without the automation now.For 2017, we’ve put together a slightly longer list.Here we go:
1. Continue to automate our tests!
What do we mean by continuing? The goal is to find time for writing more advanced test cases on the paths where bugs are frequently found - and then - automate those cases.Another thing to do is to handle the User Agent problem in Protractor - it blocks some basic test cases in one of our international projects. We need to find another tool that can help us change the User Agent so that the missing test cases could be automated.Any suggestions?
2. Improve our programming skills
Make our own repository and start learning an object-oriented language that is independent from application code. To this day, we have written everything in Javascript (Protractor and Nightwatch), we were using same repository as our dear developers. Next step? Learn Java, Python, or another object-oriented language that would be more suitable for automation and try to be more independent from the code written in Javascript. We've already written some answers for people learning how to code. Desired results? Fewer conflicts, more independence, skills improvement.
3. Improve our relationship with the developers
Of course, we are friends already, but a goal here is to make us all better understand the needs of both sides. How do we plan to do that? For starters, we’re preparing a series of presentations for the devs; we will be sharing them with Apptension’s online community as well. One of them, concerning the question of collaboration between the programmers and the testers will be published on our SlideShare soon. Another slideshow, entitled “Can QA be imperfect” is coming as well. You can also read our article about working with programmers, to get a better understanding of what to avoid.Stay tuned!
4. Take part in QA-dedicated courses
There are a lot of courses and meetings dedicated for testers and be a part of this community. Topics that we are specifically interested in:
- Python for testers - we want to have our own repository and learn an object-oriented programming language (see point 1).
- Performance testing - we haven’t had a chance to try out Jmeter yet so it will be good to learn how we can use performance tools in our projects.
5. Better summaries
Another thing is making summaries for the reported bugs rates and finding the best way to analyze them.We want to think - what are the most problematic modules in our projects? Can we do something to decrease the bug rates?Once we’re able to effectively analyze the reports, then we can try to optimize our processes.[caption id="attachment_1291" align="aligncenter" width="1024"]
Apptension's QA team.
6. Improve teamdeck
Chances are, you’ve already read about teamdeck. It’s a resource management product that we’ve built here, at Apptension. Don’t hesitate to try it out! It’s a really big achievement for everyone in the team - from PMs and designers, through developers to testers, we’ve all worked hard to make it happen. As the QA team, we want to maintain the quality of the app. We’re going to evaluate our success by measuring user satisfaction and gathering customer feedback.
7. Better estimate our time
We’ve got a plan for it - remember teamdeck? It comes with a time tracking app, which helps us check how much time we spend on specific activities: writing test cases, automating, manual testing. Such data will be very helpful in the estimating process. Comparing our estimates with actual time spent on testing will be a good way to measure our progress.
8. Eat healthy, exercise and remember about work-life balance!
Granted, most people would consider it a personal resolution, not a career-related one. Still, clean-eating, exercising and maintaining work-life balance will improve both your personal happiness and performance at work. You want to work effectively? Try to follow good lifestyle practices.
9. Grow our team
We are still a pretty small QA team and we would like to get a little bit bigger! We’re looking for someone who wants to join our team. What do we offer?
- A lot of international projects.
- A great team.
- Plenty of day-to-day achievements.
We take pride in our company’s vibe. Interested to feel it? Send us your application, and hopefully we will meet this year in the office!
Over to you
There you have it - a list of our new year’s resolutions that we think could be useful for many QA teams out there.Do you have New Year’s goals of your own? Let us know! You may also want to read:
- How Do We Use Employer Branding For Hiring IT Professionals
- QA Departments in Startups. An Open Letter to CEOs
We wish you a happy New Year!