Allowed R6 · Within policy
{
"slug": "merchant-portal-automation-task",
"title": "Merchant Portal Automation Task",
"difficulty": "medium",
"tags": [
"devops",
"qa",
"take-home"
],
"is_free": true,
"locked": false,
"frequency": 1,
"last_reported_at": "2024-03-04T09:38:14.302823Z",
"url": "https://www.mokabla.com/en/c/kashier/merchant-portal-automation-task",
"agent": {
"page": "https://www.mokabla.com/agent/en/c/kashier/merchant-portal-automation-task",
"question": "https://www.mokabla.com/agent/_call/get_question?company=kashier&question=merchant-portal-automation-task"
},
"company": {
"slug": "kashier",
"name_en": "Kashier"
},
"body_md": "## What they ask\nQA candidates get an automation task on the live merchant portal, in two flavours over the years.\n\n**Sign-up form (2022).** Automate the merchant registration page: submit with nothing filled and assert the required-field errors; fill invalid data (a numeric name, a short phone, an email without a domain, a password that fails the policy, a confirmation that does not match) and assert each validation message; then the happy path with valid data through to the next step. Candidates did it in Cypress with fixtures for the credentials, screenshots of the error states, a Mochawesome report and, in one case, visual checks with Applitools.\n\n**Payment requests (2024).** Log in to the merchant dashboard and automate the Payment Requests feature end to end: create a request with valid data; try an empty customer name and amount; a negative amount; an amount longer than eight digits; change the request currency; edit an existing request; mark a request as paid; and finally pay a request as a guest through the hosted checkout. Delivered as Java, Selenium, TestNG, Cucumber feature files with step definitions and a Page Object Model (login page, dashboard, payment requests list, edit page, payment page), with test data in a properties file.\n\n## What they look for\n- Page objects that mirror the portal (login, dashboard, the feature page, the checkout page) and a hooks class that logs in once.\n- Negative cases that are specific to money: zero, negative, too many digits, a currency change after creation.\n- The guest checkout path asserted on the payment result page, not only on the redirect.\n- Stable locators on a React dashboard where class names change, and screenshots on failure.\n- Test data that does not pollute the merchant account: unique names, cleanup, or the test mode.",
"follow_ups_md": "- How do you run this against the test environment without real card charges?\n- A step needs an OTP. What is your strategy in an automated suite?",
"access": "Question bodies are paid content: a person buys 30 days of access per company (200 EGP or 200 points) in the human app. Agents get titles, tags and difficulty; bodies only for free questions."
}