Vendventory Documentation
v1.0.0 Changelog

Clean Install Smoke

Use this checklist to validate the buyer path from a blank database. Run it once for an essential-only install and, if the package ships optional demo content, once more with demo content enabled.

Goal: prove that the app can be installed without manual rescue steps and that the first admin account can reach the core modules immediately after setup.

1) Safety Rules

Run only in a disposable environment
  • Start from a blank database or a disposable copy of the target environment.
  • Delete or rotate any previous install lock only when the environment is intentionally being re-tested.
  • Use fresh mail and session settings so password reset and OTP behavior represent the shipping defaults.

2) Pass A: Essential-Only Install

Installer walkthrough
  1. Confirm requirements page, writable directories, and environment checks pass cleanly.
  2. Provide database credentials and baseline app settings without enabling demo content.
  3. Complete the installer and verify the baseline seeders create roles, permissions, settings, and the installer-created admin account.
  4. Sign in with the first admin account and confirm the dashboard loads without errors.

3) Pass B: Demo-Content Install

Optional demo verification
  1. Repeat the install flow in a fresh disposable database.
  2. Enable the demo-content option during the installer flow.
  3. Confirm the install completes without conflicting user, category, product, or inventory records.
  4. Verify the app still lands cleanly on the dashboard and that sample master data and transactions are visible where expected.

4) Post-Install Verification

Must-open pages
  • Dashboard
  • Settings and mail configuration
  • Roles and permissions
  • Users and profile security
  • Notification dropdown and notification index
Operational smoke
  • Categories, units, suppliers, and products
  • Purchases
  • Stock outs
  • Stock adjustments
  • Reports and exports

5) Evidence Log

Record these details
  • App version, date, and environment used for the smoke pass.
  • Whether the pass was essential-only or demo-enabled.
  • Installer step where any issue happened, including the exact validation or server error.
  • First admin login result and the first page visited after login.

6) Sign-Off

A clean-install smoke pass is complete only when both the installer and first-login experience work without code edits, manual SQL fixes, or undocumented filesystem steps.