Signup / trial entry page is reachable
The public part of the funnel: GET /signup returns 200. Signup is the top of the SaaS funnel, so its reachability is checked on every run without needing credentials.
Section 23.1
SaaS Billing, Trial & Quota test pack
Signup, trials, plan gating, quotas, upgrades and suspension — the commercial lifecycle of a SaaS product, tested on a dedicated TEST-QA account.
A SaaS product can have flawless features and still fail commercially: a trial that never expires, a plan-gated module that opens for free accounts, a quota that silently lets data corrupt, or an upgrade that loses the customer's records. The SaaS billing pack tests that lifecycle as behaviour, not as screenshots.
The pack is deliberately conservative about expectations. Where a product's plan rules — quota values, trial length, suspension and retention behaviour — are not documented anywhere the platform can read, the corresponding cases are marked NEEDS REVIEW and are never asserted from a guess. Undocumented expected behaviour is never assumed; the product owner supplies the plan rules before those cases can be approved with real assertions.
The checks in this pack
Plan-gated modules show a gating / upgrade notice
On the Free Trial, gated modules (Manufacturing, Staff, Online Store and Loans on the pilot product) must show a gating or upgrade notice rather than opening — or crashing. Gating behaviour itself is the behaviour under test, never a coverage failure.
Plan quota behaviour below, at and above the limit
Products, users and shops are created up to and beyond the plan limit on the TEST-QA account. This case carries a NEEDS REVIEW note wherever the product's documented quotas are unknown, so it cannot be approved with invented limits.
Trial start and trial-expiry behaviour
What happens when a trial begins and when it expires: access, warnings and the state of the customer's data. Trial length and expiry behaviour are asserted only from documented product rules.
Plan upgrade / downgrade effects and subscription documents
Plan-state changes take effect correctly and the subscription invoice or receipt is generated. The payment itself is out of scope for automated execution — no real payments are ever made; the case covers plan state and generated documents on the TEST-QA shop only.
Suspended-account behaviour and data retention after expiry
A suspended or expired account must behave predictably at login and its data must be retained exactly as the product's rules promise. Undocumented suspension rules stay NEEDS REVIEW.
Status on each profile
| Profile | Status | Reason (from the profile definition) |
|---|---|---|
| POS / Retail | Attached | Dukaan AI is a multi-shop SaaS with signup, a Free Trial and plan-gated modules (Manufacturing, Staff, Online Store, Loans) — all observed in Oct 2026 and Phase 3. Quota values and trial-expiry behaviour are NOT documented anywhere available to the platform, so those cases carry NEEDS REVIEW notes (Section 23.1). |
| Madrasah / Masjid / Maktab | Needs review | Applies only where the specific installation is multi-tenant SaaS; single-institute deployments are not SaaS-billed. Decided per product at registration time — NEEDS REVIEW until then. |
Honest limits
Authenticated SaaS lifecycle behaviour can only be verified on a TEST-QA account, so most of this pack's cases are skeletons until credentials exist and the owner approves them with real business assertions. That blocked state is reported openly — a blocked case is never counted as a pass.
Pack checks run under the platform's standing safety rules: TEST-QA accounts and TEST-QA-marked data only, no real payments, credentials only through the secret store, and every result — pass, fail, blocked or needs-review — reported as it actually is. Read how the resulting evidence becomes a readiness score and coverage figure.