Use case: Marketplaces

End-to-end testing for marketplaces

A marketplace has two sides. Listings, messaging, payouts and disputes each involve a buyer, a seller or both.

Flows to cover first in marketplaces: listings, messaging, payouts, disputes. Each flow becomes a spec: a YAML file with plain-English steps that runs locally or in CI.

  • Each side gets its own specs with its own test credentials in env.
  • Tags split the suite, so the smoke set runs on every pull request and the full set runs less often.
  • A failed payout test gets a triage card with a proposed classification: app bug, test issue or environment.
tests/seller-listing.test.yaml
1name: Seller publishes a listing2url: https://app.example.com3tags: [listings, smoke]4env:5  EMAIL: ${SELLER_EMAIL}6  PASSWORD: ${SELLER_PASSWORD}7steps:8  - Log in with EMAIL and PASSWORD9  - Click "New listing"10  - Fill in the title, price and one photo11  - Click "Publish"12  - assert: The listing is shown under "Active listings"

Questions

Can one test log in as both buyer and seller?

A test has one env map, so it can hold both sets of credentials. Most teams keep one side per test to keep failures easy to read.

How do I run only the smoke tests?

Tag them and run npx aitp run --tag smoke.

Request early access

Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.