Does QA and Testing Qualify for SR&ED?

Quality Assurance (QA) and testing are integral parts of the software development lifecycle. However, the CRA takes a very specific view on whether testing activities qualify for the SR&ED tax credit.

To determine eligibility, you must separate routine testing from experimental testing.

Routine Quality Assurance (Ineligible)

Most standard QA practices in a software company are considered routine and are not eligible for SR&ED. This includes:

• Functional Testing: Manually clicking through an app to ensure features work as expected.
• Regression Testing: Running automated test suites (like Jest or Selenium) to ensure new code hasn't broken existing infrastructure, especially when the test scripts themselves use standard methodologies.
• User Acceptance Testing (UAT): Having beta users test the software for usability and feedback.

These activities, while critical for releasing a stable product, do not attempt to resolve a technological uncertainty. They simply verify that standard engineering work was performed correctly.

Experimental Testing (Eligible)

Testing only qualifies for SR&ED when the test itself is an experiment designed to overcome a technological roadblock.

This usually happens when standard testing tools fail, and you must build custom test harnesses or new testing methodologies to evaluate the success or failure of your primary experimental development.

Examples of Eligible Testing:

• Extreme Load Testing: If your technological uncertainty involves building a novel distributed database architecture capable of handling unprecedented transaction volumes, the custom scripts you write to simulate that massive, realistic load (and the analysis of the resulting failures) are likely eligible.
• Security Penetration Testing of Novel Algorithms: If you invented a new encryption methodology—not just implemented AES-256—the rigorous, non-standard testing required to validate its mathematical security is likely eligible.
• Hardware Integration Testing: If you are building software that interfaces with proprietary, undocumented hardware components, the trial-and-error testing required to establish and stabilize that communication protocol often qualifies.

The Documentation Burden

If you plan to claim QA activities, your documentation must explicitly uncouple them from routine software verification. You must clearly narrate how the testing phase was a direct component of the scientific method used to attack the core technological uncertainty of the project.