Dedicated quality engineering keeps a customizable recruitment cloud releasing smoothly as project scope doubles
Scaled quality assurance operations alongside a twofold expansion in development scope, safeguarding release schedules and custom multi-company configurations across web and mobile interfaces for a nationwide recruitment cloud.
PROJECT OVERVIEW
Field | Content |
Client | A company that provides a customizable recruitment business platform used by many companies |
Market | Japan |
Industry | Professional Services |
Engagement Model | Dedicated testing team |
Scale and Duration | A testing engagement covering the platform's web and mobile applications |
Core Technology Stack | Java platform, tested through web and mobile interfaces |
ABOUT THE CLIENT
This case study is based on a real VNEXT project. The client's identity and certain project details have been anonymized or generalized for confidentiality purposes.
Recruiting agencies and in house hiring teams across the country run their daily work on a platform that our customer provides. It holds the whole hiring business in one place, and each company can shape its own version to fit its strategy. For companies in professional services, that kind of system is the place where clients, candidates, and revenue all meet, which makes its reliability a business matter and not merely a technical one.
THE CHALLENGE
The platform has been in development for many years, and its business rules have grown to match. It organizes its information around nine kinds of record: clients, contact persons, jobs, people, resumes, hiring processes, activities, sales, and reports. Seven of them carry most of the work and fall into two groups, one around candidates and one around clients. Understanding how those records relate to one another takes time, and a tester who does not understand them cannot judge whether a result is right.
Because every company can shape its own system, there are many more combinations to test than a fixed product would have. A setting that works for one company's configuration must not break another's, and the testing has to keep up with that variety.
The scale of the engagement also changed quickly. Within a short period, the project grew to twice its original size, which meant bringing more people into a complex domain without letting the pace of testing slip.
PROJECT OBJECTIVE
The customer wanted a testing team that could understand a long established and intricate platform, absorb a sudden increase in the amount of work, and keep testing on schedule so that releases never waited on quality checks.
APPROACH AND METHODOLOGY
Starting each day together
From the first days of the engagement, the team met every morning, which gave everyone a daily moment to share what they had learned and to ask what they had not understood. The habit was especially valuable while the team was growing, because new members could pick up the domain from colleagues in hours rather than weeks.
Confirming understanding task by task
Our project manager went through each piece of work with the team and checked that each person understood it the same way. In a domain with so many connected records, a small difference in understanding can turn into a test that checks the wrong thing.
Reviewing the tests before they reach the lead
Testers reviewed one another's work before test documents were merged and passed to the test lead. That cross review caught gaps in coverage early, and it meant that the lead's time went to judging quality rather than correcting basics.
Keeping the overview in view
Every member was expected to understand the broad function of each development round, not just the part they were testing. Knowing how a feature fits into the whole made it much easier to see where a change might ripple.
Letting the team propose and the customer know early
Team members were encouraged to propose their own solutions, which built their ability to run their own part of the work, and any problem the team ran into was reported to the customer as early as possible.
TEAM SCALE
Our team had eight people: one project manager and seven testers, a structure that put software testing at the center of the engagement.
- Project manager: kept priorities clear, checked everyone's understanding of the work, and handled communication with the customer
- Testers: wrote and ran test cases across the web and mobile applications, reviewed each other's work, and kept test progress steady
- Test lead: reviewed the merged test documents and judged quality before results went to the customer
THE SOLUTION AND TECHNOLOGY STACK
Our contribution was a testing practice built for a platform that keeps changing and keeps being customized.
What our team provided
- Coverage across the platform's records: tests organized around the clients, jobs, candidates, resumes, processes, activities, sales, and reports that the platform manages
- Web and mobile testing: checks on both the browser based application and the mobile application
- Cross reviewed test documents: test documents reviewed by peers before they reach the lead
- A steady test cadence: daily coordination and clear task ownership so that testing keeps pace with development
Technology and tools
Area | Technology / Platform Used |
Platform under test | A Java based recruitment business platform |
Interfaces tested | Web and mobile |
Communication | Microsoft Teams |
Task tracking | The customer's task control tool |
Recruitment software is a recurring theme in our work, and a different side of it appears in our multi portal recruitment platform case.
THE RESULTS
- A customer that wants to build more with the team: the customer was pleased with the team and expressed a wish to work together on further systems.
- A team that runs smoothly on its own: once working and contact rules were agreed, the team worked well together, sometimes without the project manager needing to take part.
- Testing that kept its pace: test progress was maintained throughout, including when the project doubled in size.
- A friendly team atmosphere: the team kept a positive working atmosphere that helped newer members settle in.
When a team can double in size without losing its footing, the customer gets something more valuable than extra capacity: a testing partner it can rely on.
Kết nối với chúng tôi
Biến mục tiêu thành kết quả?
Chúng tôi sẵn sàng đồng hành cùng doanh nghiệp.
