Use Case in Software Testing: How to Turn One Into Test Cases
Every path through a use case becomes at least one test case. A worked bank-transfer example shows the test table, and ISTQB's 2023 and 2025 syllabus changes explain…
HR and Payroll Software Testing Services
Vervali tests HR and payroll platforms where an error becomes a legal problem: payroll calculation across tax tables, deductions, pro-rata and retroactive adjustments, year-end processing, onboarding and separation workflows, applicant tracking performance, benefits and time capture, and the integrations to finance and identity systems. Accessibility and security coverage are included, since HR software is used by everyone in the organisation.
150+ clients
450+ projects
275+ engineers
15+ years
ISO/IEC 17025:2017Accredited testing laboratory
CMMI Maturity Level 3The process is written down and repeats
ISO 9001:2015Quality management
ISO/IEC 27001Information security
Payroll Calculation Accuracy
Payroll is the one product where being wrong once is a legal event, so every expected value is calculated outside the system under test
using our application testing method.
Tax Tables and Jurisdiction Rules
The table that changed overnight and every jurisdiction named in the quote. We test withholding against the published rules for each one, before and after a tax-table update. We test those rules and do not issue an IRS, FLSA or ACA certificate.
Deductions and Benefits
Benefit contributions, garnishments, overtime and shift rules. A deduction that looks applied and a net that does not agree is a legal miss, not a support ticket. Expected values come from the table you named, calculated outside the product.
Pro-Rata, Retro and Year End
Joiners, leavers, a backdated change and year-end processing. A retro that silently skips a period is the case an auditor finds. Where there is no spec, we reconstruct the intended rule with your payroll owner, then test the failure cases.
What a Payroll Regression Pack Looks Like
Tax rules change every year, so the pack runs on the tax calendar as well as the release calendar.
Employee Scenarios
Salaried and hourly, multi-state, part-period, garnishment and benefit changes: every rule combination that matters. Each scenario has an independently calculated expected outcome, signed by your payroll owner.
Run Before Every Change
The pack runs before every release and every tax-table update. A stale pack is worse than none, so the quote names who keeps it current and who signs the expected values.
Automated Where Stable
Stable scenarios move into automation through our test automation practice, so the full pack can run on every build. Rules that change often stay with a person until they settle.
One wrong net pay is a legal event, not a support ticket.
Talk to a QA LeadOnboarding, Separation and Asset Workflows
The lifecycle either side of payroll, where one missed step becomes a security or compliance gap.
Onboarding
Offer, documents and the account that has to exist on day one. We test the slow vendor, the partial payload and the joiner who already started on a phone. A welcome email with no record in HR is the miss we look for.
Separation and Final Pay
Last day, access off, and the final settlement that has to match the contract. A leaver who still has a login is a security event, so access removal and final pay are tested together with the payroll engine.
Asset Recovery
Laptop, badge and the ticket that has to close. A separation that looks complete while an asset never came back is the case we test, along with the approvals and notifications around it.
Case Study
How an HR software provider took onboarding, separation and asset management off manual steps.
HR software provider · onboarding, separation and assets
Before: the client's customer base and demand were growing fast. Part of employee onboarding was already digital, but many steps were still manual, and the product had to keep improving to sustain that growth. They needed a partner that could work as an extension of their own team. Vervali took that role, helping digitise the remaining onboarding, separation and asset management processes with testing across each workflow.
Digital onboarding Separation workflows Asset management Extension of the client teamApplicant Tracking Under Volume
A careers campaign that drops applications is lost hiring, so load is modelled on your own last campaign.
Search and Matching
Filters that actually filter, matching that holds at scale, and bulk actions that do not time out. We model volume from your own last campaign, not a round number of virtual users.
Scheduling Across Time Zones
The interview that landed on the wrong clock. Calendars, time zones and the candidate who already booked on a phone. We test the conflict, not only the happy slot.
A Careers Campaign
Traffic on apply during a campaign. Login that stays up while apply fails is a failed campaign, not a green report. Load runs through our performance testing practice.
The Integration Surface
A malformed payment file is a payroll that does not run. Every integration is tested for the slow or unexpected response.
The Payment File
The file the bank has to accept. A net that looks right on screen and a file the bank rejects is a payroll that does not run. We test the format, the retry, and the case where a row was dropped.
Finance and Benefits
General ledger, benefits providers and time capture. Timing windows, duplicate posting and the slow vendor, covered through our API testing services. Named systems go into the test design after NDA.
Identity
SSO, provisioning and the leaver whose access never turned off. Partial payloads are the usual miss. If we have not tested a provider before, we say so before we quote.
Every employee uses your HR system, including employees with disabilities.
Free Accessibility AuditAccessibility Is an Obligation, Not a Nice-to-Have
An HR system every employee has to use is an accessibility obligation, and public-sector employers carry the same duty as their public site.
What We Test
Payslips, leave requests, benefits enrolment, onboarding forms and self-service, with NVDA, JAWS, VoiceOver and keyboard only, against WCAG 2.2 AA or the level you named. Audits, VPAT support and deadlines are covered by our ADA and Section 508 compliance testing.
Public-Sector HR Experience
Our strongest accessibility engagement was for a public-sector HR software provider: 2,000+ URLs audited and Section 508 certification on the first attempt, inside the committed 90 days. The same method applies to your employee-facing flows.
Security and Personal Data
HR systems hold identity documents, bank details, salary and health data, one of the densest stores of sensitive data in any business.
Access Between Roles
Manager and employee boundaries, admin rights, and what each role can see or export. Retention and deletion rules are tested against your policy. Application and API attack work runs as a separate security testing engagement.
Regulatory Controls
HIPAA when health data is in the path, PCI DSS when card data moves, GDPR when you named it. We test those controls through our compliance testing practice and do not issue those certificates. Vervali tests SOC 2 readiness and does not hold that certification.
Test Data Handling
We will not copy production employee records into a test environment. Synthetic or masked data is agreed before anything is signed, under Vervali's ISO/IEC 27001 certified information security.
How an Engagement Starts
From one HR flow to a regression pack on your tax calendar, 9am to 1pm Eastern with delivery from India.
-
01
Share the Platform
Tell us the products in play (payroll, onboarding, ATS, benefits, time), the tax-table calendar and the jurisdictions, with staging access under NDA.
-
02
Agree Data and Coverage
Data access is agreed first. You then get the coverage model, the jurisdictions in scope, and whether the payroll regression pack starts in the same week.
-
03
Start With One HR Flow
A free accessibility spot audit of one HR flow is the fastest first look at our findings. If you already know the platform, a QA lead scopes the full engagement.
-
04
Keep It Current, Build What's Next
We keep the pack current as tax tables and releases change. Development comes second: the same team can build or extend payroll, onboarding and applicant tracking through our HR and payroll software development, with testing inside every sprint.
Frequently Asked Questions
We calculate every expected value outside the system under test, from the tax tables, deduction rules and contracts you name. Scenarios cover tax tables by jurisdiction, deductions and benefits, overtime, pro-rata for joiners and leavers, retroactive adjustments and year-end processing. Where there is no written spec, we reconstruct the intended rule with your payroll owner and test the failure cases as well as the correct ones. A payroll test that reuses the system's own arithmetic proves nothing.
We test against the rules you operate under: federal and state tax withholding, FLSA overtime, ACA reporting fields, HIPAA where health data is involved, PCI DSS where card data moves, GDPR where you named it, and WCAG 2.2 AA or Section 508 for accessibility. We test those controls and produce the evidence. We do not issue IRS, FLSA or ACA certificates, and Vervali tests SOC 2 readiness without holding that certification.
We build a set of employee scenarios covering every rule combination that matters, each with an expected outcome calculated independently and signed by your payroll owner. The pack runs before every release and every tax-table update, because tax rules change every year and a stale pack is worse than none. Stable scenarios move into automation, and the quote names who keeps the pack current.
We test access control between roles, manager and employee boundaries, export rights and retention rules, because HR systems hold identity documents, bank details, salary and health data. Production employee records are never copied into a test environment, and synthetic or masked data is agreed first. Vervali holds ISO/IEC 27001, and application or API attack work runs as a separate security testing engagement on agreed assets.
Yes. We load search and matching, bulk actions, interview scheduling and the apply flow on the careers site, modelled on your own last campaign rather than a round number of virtual users. The report shows where response times break and which component causes it, so your engineers fix the bottleneck that drops applications, not only the login page that stayed up.
Yes. We test the integrations HR and payroll depend on: the bank payment file, general ledger, benefits providers, time and attendance, and identity and SSO. Each is tested for format, retries, duplicate posting and behaviour when the provider is slow or returns something unexpected. A malformed payment file is a payroll that does not run, so that path gets the most coverage.
Yes. An HR system every employee has to use is an accessibility obligation, and public-sector employers carry the same duty as their public site. We test payslips, leave, benefits enrolment and onboarding with NVDA, JAWS, VoiceOver and keyboard only, against WCAG 2.2 AA or the level you named. Our strongest accessibility engagement reached Section 508 certification on the first attempt for a public-sector HR software provider.
Yes. Employees check payslips, request leave, capture time and complete onboarding on their phones, so we test those journeys on real iOS and Android devices. Coverage includes poor-network behaviour, push notifications, biometric sign-in and accessibility with VoiceOver and TalkBack. A responsive website that passes on desktop does not prove the app, so the app is tested as its own product.
We test the full lifecycle: offer, document collection, account provisioning on day one, then separation, access removal, final settlement and asset recovery. Each step is checked for slow vendors, partial payloads and the handoffs between HR, IT and payroll. A leaver who still has a login is a security event, and a final settlement that does not match the contract is a legal one.
Email Us
Call Us
