Jest Test Suite for ATS
Budget: $8 – $15 AUD
I need an experienced JavaScript test engineer to strengthen the automated test suite of my Applicant Tracking System. The codebase already contains a set of Jest tests, but they lag behind recent feature work and no longer give me the confidence I need. Your main focus will be to refactor and extend those existing tests, concentrating on two core areas:
• User authentication—covering log-in, session handling, permission checks, and any edge-case flows.
• Applicant management—every action from profile creation through status changes, all the way to archival.
Within those domains I expect thorough coverage of the application’s security features, user-facing interface behaviour, and the database interactions that back each operation. React Testing Library, Supertest, or similar helpers can be introduced as needed, as long as they integrate cleanly with the current Jest setup.
Deliverables I will review and accept:
1. Updated test files with meaningful, self-describing assertions and mocks.
2. New tests that exercise missing paths and failure conditions.
3. A concise README section or inline comments explaining any new utilities or helper functions you add.
All development happens in a Git-based workflow; please be comfortable working on a feature branch and raising a clean pull request. Continuous Integration is already wired to run yarn test, so the suite must pass there before I merge.
If you have a track record of bringing legacy Jest suites back to life and driving up coverage on authentication-heavy apps, let’s talk.
• User authentication—covering log-in, session handling, permission checks, and any edge-case flows.
• Applicant management—every action from profile creation through status changes, all the way to archival.
Within those domains I expect thorough coverage of the application’s security features, user-facing interface behaviour, and the database interactions that back each operation. React Testing Library, Supertest, or similar helpers can be introduced as needed, as long as they integrate cleanly with the current Jest setup.
Deliverables I will review and accept:
1. Updated test files with meaningful, self-describing assertions and mocks.
2. New tests that exercise missing paths and failure conditions.
3. A concise README section or inline comments explaining any new utilities or helper functions you add.
All development happens in a Git-based workflow; please be comfortable working on a feature branch and raising a clean pull request. Continuous Integration is already wired to run yarn test, so the suite must pass there before I merge.
If you have a track record of bringing legacy Jest suites back to life and driving up coverage on authentication-heavy apps, let’s talk.
Related categories:
PHP
JavaScript
Testing / QA
Test Automation
Website Testing
Git
Continuous Integration
API Testing