Whenever you look at a job vacancy, there is a typical list of requirements and responsibilities and only a few lines of what it will be like to work in this particular company. Undoubtedly, that’s what the vacancy description is for—to give a general understanding of the job. However, to receive more information on how your work will be organized, you have to at least get to the interview stage of the hiring process.
This article will provide you with an inside look at what Astound’s Quality Assurance team looks like, and what roles and testing directions we have. Besides, you will learn about the experience of a QA specialist at Astound firsthand—from our team members. Read on!
- QA Team’s Work in a Nutshell
- QA Department’s Structure
- Manual Testing
- Test Automation
- Performance Testing
- Security Testing
- Accessibility Testing
- Key to the QA Team’s Success
First off, here is the helicopter view of the team and their experience:
- Includes 280+ professionals—over 35% of whom are ISTQB-certified
- Have worked on 3,000+ projects
- Average Customer Satisfaction Rating (created by Salesforce)—9.5 out of 10
- Types of testing practices: Functional, Accessibility, SEO, API, Integration, Test Automation, Performance, and Security Testing
- 10+ different platforms: Salesforce cloud-based solutions (including Headless, Marketing, Community, Service, Integration [Mulesoft], Sales Clouds, and others), WebSphere, Netsuite, Mobify, Hybris, Magento, Core Media, and others.
And here’s the review of the QA Department’s structure. Below, we’ll examine its main elements.
Let’s start with the QA Engineering Management team. QA Engineering Managers help team members with growth and professional development. They are also responsible for putting together a project team, which is usually done with consideration not only of the individuals’ skills, experience, and personality but also of their preferences.
Our QA Trainer Team organizes external and internal training activities—workshops, meetups, boot camps, etc. Plus, our QA Trainers also prepare our colleagues for ISTQB certification.
A QA Lead sets up the processes within the QA project team and conducts communication with the Project Manager, the client, and all the other Leads on the project. Such experts manage the team, their motivation, and the QA part of the project, while optimizing processes and creating artifacts. The Lead also supports team members if they get stuck on a challenging task.
Senior QA Leads perform all of the same functions, but they should also be able to recommend a testing solution vision and architecture on the project level, rationalize and communicate architectural changes, and provide QA audits and reviews of the testing processes within projects. Senior QA Leads also conduct training activities and optimize the work of the department by suggesting new approaches, processes, and templates.
QA Technical Practice Leads (TPLs) provide all kinds of technical support. They mentor other team members who aren’t actually Leads (Middle+ and Senior specialists), but are taking a leading role on a particular project. TPLs themselves work as Leads on a project from time to time so as not to lose technical expertise.
Another part of TPLs’ work is their discussion with QA Leads on the experience, challenges, and communication cases on projects. These conversations usually result in the new best practices to be used on the next projects. TPLs also conduct training activities, optimize the work of the department, and suggest new approaches and templates.
A QA audit is performed by TPLs whenever there is a request from an Engineering Manager or a project team. The main purpose is to analyze the QA work on a particular project and provide the list of must-have action items or things to improve that can be applied either to this project or future ones. There is a specific audit procedure with a list of questions, but it’s flexible—new questions can be added if necessary. QA audits have played a major role in achieving our outstanding customer satisfaction rating of 9.5 out of 10.
QA as a service implies that our QA team doesn’t participate in the project from the start. Instead, they are hired to provide a QA service on a certain phase. An example of this would be User Acceptance Testing (UAT). It’s performed in the pre-production phase (acceptance of the project). Our team writes the UAT procedure, approves it with the client, and then provides the support. The client goes on to test the product from the business side.
As for our different testing directions, it’s better to hear about them from our QA team members. You’ll read their stories and learn what fascinates them about the specific testing practice they specialize in: Manual, Automation, Accessibility, Security, and Performance Testing.
Yuriy Logoyda joined Astound as a junior specialist with minimum experience in 2011 and advanced to the position of a Manual QA Lead in just five years.
He states that while nowadays people consider automation to be a necessary part of the QA process for all projects, the smart use of all testing types is the right choice:
“For small projects the use of automation is not reasonable, while manual testing can provide more benefits. Due to the constant change in technologies and top-selling sites dictating the rules of success, the life of the site redesign period is really short. Manual QA that is quickly adaptive to the new changes is the right choice to perform fast testing of new features.”
Yuriy also notes that the human factor of manual testing allows engineers to find things that could be missed in the process of design planning:
“Manual QA engineers can act as real customers—we can share our opinion and provide arguments—and that helps our clients to come up with the best solutions and improve their sales.”
Georgi Georgiev had been interested in automation ever since he joined the company as a Junior Manual QA Engineer. Having grown to a Middle position, he discussed his willingness to become a Test Automation (TA) Engineer with his manager, who supported him and assigned him a coach. Step by step, with the help of the coach, he studied the basics of test automation. He then became first a Junior and later a Middle TA engineer. Of course, his journey isn't over and there is much more to learn and explore.
Georgi has shared why he enjoys working in test automation:
“What I love about automation is that programming and testing are intertwined—I am looking for the middle ground between what I want to do as a QA specialist and what’s best to do as a programmer. I enjoy using machine power to additionally help and support the QA team during their already busy days.”
He also adds that when used correctly, automated tests show their real power in terms of execution speed (including parallelism) and accuracy (a machine will always do what it's instructed to, and it’ll never get tired or distracted).
“Without the performance testing, you never know the site’s performance level and what should be improved. Users expect webpages to load as quickly as possible. And if it doesn’t happen, they get frustrated and leave. Also, if a website isn't ready for Black Friday, it may crash once the amount of users increases rapidly, and the client won't get the expected sales.”
Oleksandra Zhmurko was among those who built our performance testing processes from scratch. At Astound, she had first been a Manual QA Engineer, then a Lead until 2017 when she first became acquainted with performance testing, and for the next two years she combined leading teams and doing performance testing work. Now, Oleksandra is a Performance Test Engineer Lead.
It all started when her team stumbled upon a performance issue on a Magento project. That’s when Oleksandra first thought about diving into performance testing. Later, she and a couple of other team members got to work on a first performance QA project.
“Since that time our team has already worked on plenty of exciting projects—simultaneous load testing of 10 sites, a high load project with up to 80,000 concurrent users, a project with Headless SFCC, and many others, more than 25 in total. Each project brings something new and gives the opportunity to continue learning.”
And no project can be a success without a strong team. For several years now, Oleksandra and Roman Rak have been developing the performance testing department. Currently, the team consists of six members.
“The online retail market is booming, with worldwide ecommerce sales having reached almost $4 trillion by the end of 2020. And this kind of success attracts unwanted attention in the face of cyber-criminals. Good reputation is valuable for the clients, so it's important to assure the web shops' safety for end users and the site owner. The main goal of security testing is to identify the threats in the system and measure its potential vulnerabilities, so the threats can be encountered and the system does not stop functioning.” — Vitaliy Taradayko, Security QA Lead, comments on the value of security testing.
For Vitaliy, this journey began when the QA department announced the initiative to implement security testing.
“At the time, there was a lack of information on security testing, so I had to do most of the research myself. However, this challenge pulled me into the process even more, and I practiced testing the company sites every day after work. Eventually, I've tested more than 25 sites.”
Vitaliy's Engineering Manager noticed his efforts, and together they thought of how they could develop security testing into a separate service. It was decided to launch an internal boot camp where Vitaliy would share his knowledge and experience to those interested. As a result, two boot camps have already given us a number of skilled Security QA engineers, who, together with Vitaliy, have now contributed to the success of several Astound projects.
This testing direction ensures that websites, tools, and technologies are designed and developed so that people with disabilities can use them. More specifically, this testing ensures these people can perceive, understand, navigate, interact with the Web, and contribute to it.
Yevhenii Poliakov, Engineering Manager, has helped build the accessibility testing practice at Astound from scratch.
“On my project, I introduced accessibility analysis as a mandatory part of each requirement analysis session. Also, Accessibility Testing is now a part of testing activities for each functionality.”
Yevhenii also created an onboarding program for QA engineers, prepared artifacts and tools, and conducted several training sessions.
“It is important because it’s a social responsibility to make content available for all users. Plus, non-compliance can mean reputation and financial damage as accessibility is supported by law in a lot of countries. Around 2,000 accessibility lawsuits are processed each year.”
Key to the QA Team’s Success
Our Technical Practice Lead Olena Kovalova notes:
“In the QA department, all new thoughts are welcome. You should always look at the templates or processes critically, not just blindly follow them, and if you think something could be improved somehow, everyone will be ready to hear out your idea.” That’s the secret ingredient to the Astound’s QA success.
Contribute your own ideas to our QA team, grow and develop together with us! We now have several job openings!