Skip to content
AJAIAJAI
Request a quote

Starts mixed

Usual mix in Growth · After a change, or on a schedule — login, checkout, or the screens you named — or when you paste a checklist, if the app is not connected yet.

QA

Clicks through your important screens after a change, writes down what broke, and how to see it. You set whether it only drafts the notes or also runs the checks on its own.

Request a quote for this job
Needs
A checklist, the site or app to test, the screens you named, and a login for a test account. You can start by pasting in chat.
Delivers
Pass or fail notes, how to see the break, and the odd case flagged — filed, if you set that.
You stay in charge
You set whether it only drafts, waits for a named person, or runs the checks on its own. Connect is optional.

Used for

  • Monday after the course deploy

    A continuing-education provider on Monday: they shipped a change on Friday and the booking path is on the checklist. The worker clicks the screens you named and writes down what broke. You choose whether those notes stay as a draft, or whether the run happens after every change. People still decide whether to roll back.

  • The same checkout walk

    An outdoor webshop runs the same checkout path every night, same test account, same three screens you already wrote down. The worker finishes that known walk and flags a miss. You can keep it on drafts, or let it run on the schedule so nobody finds out in production that pay died.

  • The property-software checklist

    A property-software firm has connected the test account. Login, a consent change, and the packages page sit in one checklist; the worker stages pass or fail notes in the tools you already use. You set whether it stops at the note or also runs after a deploy. Paste in chat is still enough if you have not given access yet.

  • A live break at the conference

    A conference organizer sees a payment or login fail that looks like a live outage. The worker does not invent a fix or new prices. It writes how to see the break and leaves what to ship next with a person — unless you explicitly say that kind of note may also file on its own.

  • Monday at the winery shop

    A winery on Monday: they changed a product page on Friday and the add-to-cart path is on the checklist. The worker clicks the screens you named and writes down what broke. You choose whether those notes stay as a draft, or whether the run happens after every change.

  • The same morning order

    A bakery chain runs the same morning order path, same test account, same three screens you already wrote down. The worker finishes that known walk and flags a miss. You can keep it on drafts, or let it run on the schedule so the first customer is not the one who finds it.

  • The language-school staging

    A language school has connected the staging login. Booking, a consent change, and the course page sit in one checklist; the worker stages pass or fail notes in the tools you already use. You set whether it stops at the note or also runs after a deploy. Paste in chat is still enough if you have not given access yet.

  • A live number at the energy desk

    An energy consultant sees a calculator or quote screen that looks live-wrong. The worker does not invent a fix or a new figure. It writes how to see the break and leaves what to ship next with a person — unless you explicitly say that kind of note may also file on its own.

Who does this today

Whoever currently runs a checklist before a release, or after a change. The person who still walks checkout at night, and who finds out in production that pay died.

What it does not do

It does not invent a fix, a rollback, or new prices. You set whether it only drafts the notes or also runs the checks on a schedule. What to ship next stays with a person — until you move that setting.

Related jobs

Request a quote for this job