QA Rating

Best Salesforce QA companies in 2026

QA Rating is published independently, and its publisher owns no company listed in this catalog.

8 testing companies in this catalog list Salesforce among the frameworks and tools they work with. They are grouped below by what each is best suited for, in 8 groups. 0 of them hold a certificate confirmed by a register entry and 4 publish a rate card. Composition and order last changed on September 6, 2026.
8 companies. Ordered by the number of verified reviews on external platforms, highest first. Companies with an equal count are ordered by name.

The companies

Salesforce: 8 companies, grouped by what they are best suited for.
#CompanyCase studiesPublished ratesTeam sizeReviews
Automation first Test automation is offered as a service, and at least one published case study reports a coverage or regression time metric.
1QASource11000 or more people29
2Luxe Quality251-200 people21
32i3Not published51-200 people0
Embedded team model The dedicated team engagement model is offered, and at least one published case study.
1QASource11000 or more people29
32i3Not published51-200 people0
Nearshore for the EU At least one delivery location in the EU or the EEA, or in Ukraine, Georgia, Serbia or Moldova.
2Luxe Quality251-200 people21
4QATestLab2501-1000 people17
Performance engineering Performance testing is offered as a service, and at least one published case study reports a throughput or latency metric.
1QASource11000 or more people29
4QATestLab2501-1000 people17
Device lab coverage A published device lab of 100 real devices or more, with a source.
4QATestLab2501-1000 people17
Fast onboarding A published onboarding time of 14 days or less, with a source.
4QATestLab2501-1000 people17
Nearshore for the USA At least one delivery location in Canada, Mexico, Central America or South America.
1QASource11000 or more people29
Security focus Security testing is offered, together with either penetration testing or a verified ISO/IEC 27001 certificate, and at least one published case study.
4QATestLab2501-1000 people17
Other companies in this axis No applicability tag met its criterion for these profiles.
5Indium Software1Not published1000 or more people21
6Testrig TechnologiesNot published51-200 people7
7BugwolfNot publishedNot published11-50 people0
8RTTSNot publishedNot published51-200 people0

Which contract shape keeps up with a platform that updates itself three times a year

Two of the eight companies here publish the Dedicated team engagement model: QASource and 2i. A Salesforce org does not stay still between engagements; three scheduled platform releases a year touch validation rules, page layouts and API versions nobody on the buyer's side asked to change, and a team that stays assigned across that calendar catches drift that a fresh team has to rediscover each time. QATestLab and RTTS both publish Managed testing service, where the vendor runs the engagement to its own process rather than embedding people into the client's. Testrig Technologies publishes Staff augmentation and Project work, a shape suited to a scoped migration rather than a standing watch over configuration drift. Bugwolf publishes only Crowdtesting, a pool of testers picking up short, self-contained tasks, which fits a pre-release UAT sweep better than a permission-set or approval-flow review that depends on knowing how the org was built. Luxe Quality and Indium Software publish no engagement model, so this comparison cannot be run on either without asking first.

What a published case study says was actually configured

Salesforce sits in the framework list of all eight companies on this page, since listing it is the condition for appearing here, but a framework list is not a project record. Only two companies point to a case study naming Salesforce work directly: QASource's covers a legacy CRM migrated onto Salesforce for a cancer diagnostics client, and Indium Software's reports a banking client's Salesforce application, roughly 900 test cases delivered by a ten-person team over 40 days. The other three companies with a published case study describe different systems entirely: 2i's three cases cover a Scottish benefits programme, a new bank's launch and an Oracle EBS to Oracle Fusion migration; QATestLab's cover a radiology portal and an ecommerce load test; Luxe Quality's cover an ecommerce platform and a telecom account. None of those five names Salesforce as the system under test. A framework entry says the tool sits somewhere in the stack; it does not say which engagement it is attached to, and on a platform where the actual work is bespoke configuration, that gap is worth closing with a direct request for a Salesforce-named reference before the framework list is treated as settling it.

What a lower minimum project size buys on a Salesforce engagement

Four of the eight companies publish a minimum project size, spanning a five-fold range: QATestLab at 5,000 USD, Luxe Quality at 10,000 USD, and both QASource and Testrig Technologies at 25,000 USD. The same four publish a blended hourly rate, three in the 25 to 49 USD band and Testrig Technologies under 25 USD. Salesforce work is not always a full build: a validation-rule audit before a release, or a check of one broken approval flow, is a different purchase from a re-platforming project, and a 5,000 USD floor admits the first kind of engagement in a way a 25,000 USD floor does not. The four companies with no published minimum are not necessarily pickier about size; the field is blank, and the only way to learn the floor is to ask.

Does a device lab count for anything when the screen is a browser tab

QATestLab is the only company on this page with a published device lab, 500 real devices confirmed with a source. That figure answers a question about native mobile apps tested across many handsets and OS versions. A Salesforce org is reached through a browser or the mobile client, and what breaks in it is a permission set, a record type, an approval flow or a validation rule written by whoever configured that org. A screen rendering differently on device number 400 is the failure a device lab is built to catch, a failure this axis rarely produces. The count says nothing about how well a vendor reads someone else's object model or flow logic, the actual skill this axis is meant to surface.

What four companies with no tag here have actually shipped

Testrig Technologies, Bugwolf and RTTS, together with Indium Software, hold no applicability tag on this axis, four of the eight companies listed here. That is not a verdict on their Salesforce work: Indium Software's own case study is the most explicitly Salesforce-named one on this page, and the other two publish named enterprise clients elsewhere on their sites. RTTS lists five, including Ford Motor Company, Boeing and Adobe Inc., and Bugwolf lists ten, including National Australia Bank, Westpac and HSBC, organizations large enough to run Salesforce at scale even though neither profile ties a named client to Salesforce work specifically. Every condition behind every tag on this axis is written out on the methodology page with the exact fields it reads; an untagged profile is one where those fields are not filled in yet, not one tested against a condition and failed. The services, frameworks, rates and case studies on an untagged profile stay comparable field by field against the four that do carry a tag.

How this ranking was put together

Membership is computed from the profile, not chosen: companies appear here when they list Salesforce among the frameworks and tools they work with, as their own profile states. Position in a ranking cannot be bought. Paid options are limited to the extended profile, labelled sponsor slots and lead forms, and none of them affect tags or order.

The table compares the fields that decide this axis: case studies, published rates, team size, plus the number of verified reviews on external platforms. Rates, minimum project size and onboarding time carry the source they came from next to the value.

  • Automation first: Test automation is offered as a service, and at least one published case study reports a coverage or regression time metric.
  • Embedded team model: The dedicated team engagement model is offered, and at least one published case study.
  • Nearshore for the EU: At least one delivery location in the EU or the EEA, or in Ukraine, Georgia, Serbia or Moldova.
  • Performance engineering: Performance testing is offered as a service, and at least one published case study reports a throughput or latency metric.
  • Device lab coverage: A published device lab of 100 real devices or more, with a source.
  • Fast onboarding: A published onboarding time of 14 days or less, with a source.
  • Nearshore for the USA: At least one delivery location in Canada, Mexico, Central America or South America.
  • Security focus: Security testing is offered, together with either penetration testing or a verified ISO/IEC 27001 certificate, and at least one published case study.

The criteria for this axis are on the methodology page, together with field definitions and the rule for editorial order. Changes of order are recorded in the changelog.

Questions

How soon can a Salesforce testing engagement actually start once a vendor is chosen?
Only one of the eight companies here publishes an onboarding time: 3 days. The other seven state no onboarding figure at all. That gap sits in what got published: a vendor can grant sandbox access within days and simply never have put a number on its site. The published 3 days belongs to one profile and does not set a norm for the rest; a shortlisted vendor's own figure, and its definition of "onboarding," matters more, since a system-access grant and a fully briefed admin are not the same milestone.
Which country's law governs a services contract with a Salesforce testing vendor?
The eight companies split five ways by headquarters: three in the US, two in India, and one each in Cyprus, the UK and Australia. A services agreement is ordinarily signed by the entity registered at that address, so the governing law and dispute venue named in the contract track headquarters rather than team size or price. Two candidates quoting the same blended rate can still route a dispute through two different court systems, and a shared time zone with a vendor's sales team says nothing about which of those systems applies.

Other axes these companies appear on

How to choose a vendor on this axis

Published by QA RatingPublished on September 6, 2026Updated on September 6, 2026

Every fact about a company comes from a listed source. A field without a source stays empty. A certificate counts as confirmed only when a registry, certificate or auditor report backs it; a certificate the company only claims about itself is published separately, under that label. Vendors can request a correction at hello@qa-rating.com. A correction is applied when it comes with a public source.