Project description
We operate a B2B portal used every day by our partners and account managers, and we ship updates roughly twice a month. Each release we test the same critical paths by hand, it eats a full day of a manual tester's time, and things still slip through because a human gets tired and skips a step. We want to replace that ritual with an automated regression suite that runs before every release and tells us clearly whether the core scenarios still work.
The suite must cover the login flow with valid and invalid credentials and a locked account, the full request-submission path from an empty form to a confirmed record, and role-based access so that a partner never sees a manager's screens and a manager cannot reach the administration area. We would like the tests to run against a staging copy of the portal, produce a readable report showing which scenarios passed and which failed with a screenshot at the point of failure, and be launchable both by hand and from our build pipeline with a clear exit code.
We expect clean, maintainable test code that a new engineer can extend, stable selectors that do not break on minor markup changes, and short written notes on how to add a new scenario. Deliverables include:
— login scenarios covering success, wrong password and a blocked user;
— end-to-end request submission with field validation;
— role and permission checks for partner, manager and admin;
— a readable report and a pipeline-friendly exit code.
The suite must cover the login flow with valid and invalid credentials and a locked account, the full request-submission path from an empty form to a confirmed record, and role-based access so that a partner never sees a manager's screens and a manager cannot reach the administration area. We would like the tests to run against a staging copy of the portal, produce a readable report showing which scenarios passed and which failed with a screenshot at the point of failure, and be launchable both by hand and from our build pipeline with a clear exit code.
We expect clean, maintainable test code that a new engineer can extend, stable selectors that do not break on minor markup changes, and short written notes on how to add a new scenario. Deliverables include:
— login scenarios covering success, wrong password and a blocked user;
— end-to-end request submission with field validation;
— role and permission checks for partner, manager and admin;
— a readable report and a pipeline-friendly exit code.
Software development Cash, Bank transfer
