The testing flow
Open a question → ask the OI → upload a screenshot → describe what happened → choose the result → save.
The question, screenshot upload, comments and coloured results are on the same card in My testing and Question bank. Screenshots can be chosen, dragged or pasted. Testers are not asked for a software build, version, environment or session setup.
Names and timestamps are automatic. Any number of questions can be tested; completing all 116 is not required. Cost, timing, source and token details are optional.
For a personal trial, open the included HTML preview. Its sample results are labelled, and its data stays in the current browser. It does not send results to the shared server. Back up before clearing local data.
For Brijesh and the server team
- Confirm the cPanel account supports Node.js 22.13+ and PostgreSQL 16+ locally or through an approved external connection. Confirm the supported application startup method, HTTPS and environment settings.
- Keep the source tree and credentials outside public_html. Configure DATABASE_URL and APP_URL using your server's environment/secret settings. Use cpanel.env.example as a reference; replace every placeholder.
- Install dependencies, create the schema, add the question bank, create the first administrator and build the application.
- Start the application through the hosting provider's supported process manager. The standalone startup command below serves port 3000 unless PORT is set. The provider must configure its proxy/startup arrangement.
- Run the acceptance checklist with two testers and one engineer before inviting the whole team.
npm ci
npm run db:migrate
npm run db:seed
npm run admin:create
npm run build
npm start
The plain Node setup scripts require variables in the process environment; merely copying an .env file is not sufficient for those scripts. The app supplies no default administrator password.
Use cliff@hyphenconnect.ai for Cliff's administrator account if agreed. Testers receive individual accounts, not the preview's demo profile selector.
Docker files remain an optional VPS deployment route. Do not assume Docker is available on a shared cPanel account. Read cPanel notes and installation instructions.
One complete pack
| File or folder | Purpose |
|---|
| app / lib | Next.js/React interface, API routes, permissions, workflows and PostgreSQL access. |
| database/001_initial.sql | Schema for the migration command. |
| database/questions.json | 116 starter question definitions. Administrators can add/edit questions. |
| database/oi_test_centre_complete.sql | Alternative fresh database schema plus the 116 questions. Use this OR migrate + seed; not both. |
| scripts | Database migration, non-destructive question seed, administrator creation, startup and backup. |
| OI_Test_Centre_Personal_Preview_v2.html | Matching offline personal preview. No real shared accounts or server synchronisation. |
| docs | cPanel setup notes, API integration, operations, technical design, validation and acceptance checklist. |
| tests | Workflow, rendered-form and HTTP checks. |
Screenshot and document bytes are stored in PostgreSQL in the shared application, alongside their ownership and evidence links. A database backup therefore includes uploaded files.
Before live testing
- Upload the actual 01 to 011 documents, rules and quick-answer reference files through Documents. These private source files are not included.
- Link questions to the correct database document records through Edit question. Changing a document code must use Replace/change code on the same record.
- Add testers and technical users in People, then verify access and screenshot downloads.
- Configure backups. Restore one backup to a separate database and check an uploaded image.
- Optionally configure OI_BUILD and OI_TEST_ENVIRONMENT behind the scenes. Leave unknown values blank. A Pass with unknown release metadata does not automatically certify the technical fix.
- Connect the optional telemetry API if automatic search measurements are needed. Until then, enter observed costs/times manually.
The code package is ready for installation and staging checks. It is not already installed or certified on your cPanel server. The included validation document distinguishes automated checks from checks your team must complete on your infrastructure.
No automatic screenshot judging, document ingestion into the OI, email delivery, SSO, external ticket integration or hosted-data migration is claimed.