Features list

Core testing methodology

  • Proxy-based architecture – Yesbot sits between frontend and backend, observing real traffic passively
  • Traffic tracking / tracking tests – learns from actual user journeys and API calls rather than synthetic scenarios
  • API auto-discovery – automatically discovers backend API endpoints (available from “Lvl 1 Back” configuration up) Yesbot can have 4 different feature levels, increasing its power, but also requiring more configuration on the side of the tested applications
  • Edge case generated tests – algorithmic generation of boundary/edge-case scenarios
  • LLM-generated tests – AI-driven test authoring, available at the more advanced configuration levels
  • Read-only test generation – safe-by-default test generation that doesn’t mutate data
  • Write test generation – full read/write test coverage (only at the most advanced “Lvl 3 Back” experimental tier) Frontend configuration Yes. Backend configuration Advanced. Tracking tests Yes. API auto-discovered tests Yes. Edge case generated tests Yes. LLM generated tests Yes. Read only tests Yes. Write tests Yes

Data & state management

  • Automatic database state management for idempotent write-test replay (currently MySQL-scoped)
  • Dependency-aware test sequencing to keep write operations safe and repeatable

Editing & control

  • Direct JSON editing of generated test scenarios in the UI – humans can inspect/modify what the AI generated rather than treating it as a black box

AI/model flexibility

  • BYOK (Bring Your Own Key) – customers can plug in their own LLM provider instead of being locked to Yesbot’s default model

Deployment options

  • Cloud SaaS – default hosted execution
  • On-premise via Testbot – a standalone executable (compiled with Bun) that users can download and run on their own servers for test-data privacy, with account-level entitlement tied to their usage plan

Account & platform management

  • Multi-application support – manage tests across several applications under one account
  • Quota management – usage plans based on test scenario count and application count, with add-on quota purchases without a full plan upgrade
  • Usage plans (currently including an “XL” tier) with a pricing matrix based on applications × scenarios

Product stage

  • Alpha / early access – Yesbot is explicitly positioned as an actively developed alpha product; early-access users are given a disclaimer about work-in-progress features and encouraged to use test/sample data rather than production data

Categories:

Tagged:

Comments are closed