Since the I18nextProvider is already set up in our unit test render function, we are good to use the t() function in our unit tests. I switched over 3 unit test files in this PR as a POC. We can do the rest as time allows.
I updated the unit test documentation with a new section on using translations in unit tests. I also updated all the examples in the docs appropriately.
Screenshots/Video
Testing
[ ] Tested on iOS
[ ] Tested on Android
Reviewer Validations
Unit tests can use translations instead of just strings
Documentation is updated appropriately
PR Checklist
Reviewer: Confirm the items below as you review
[ ] PR is connected to issue(s)
[ ] Tests are included to cover this change (when possible)
[ ] No magic strings (All string unions follow the Union -> Constant type pattern)
[ ] No secrets or API keys are checked in
[ ] All imports are absolute (no relative imports)
[ ] New functions and Redux work have proper TSDoc annotations
alexandec
commented
2 days ago
Description of Change
Since the I18nextProvider is already set up in our unit test render function, we are good to use the t() function in our unit tests. I switched over 3 unit test files in this PR as a POC. We can do the rest as time allows.
I updated the unit test documentation with a new section on using translations in unit tests. I also updated all the examples in the docs appropriately.
Screenshots/Video
Testing
Reviewer Validations
PR Checklist
Reviewer: Confirm the items below as you review
For QA
Run a build for this branch