Planning handoff complete
Define the testing process
The project brief, proposed participation rules, database design, and work plan are documented. Final product decisions remain open with Seth.
Connection details
Share these details when reporting a loading problem. They contain request names, status codes, timings and request IDs, without names, reports, cookies or sign-in tokens.
WORKSPACE / PEOPLE & ACCESS
Admin panel
Invite people and choose what they can do on the website.
Sign-in setup needed
Connect real sign-in to manage users
This local demo uses sample identities. Choosing Demo Developer does not grant administrator permissions.
Your initial owner account will become the first Super admin after email-and-password sign-in is activated. Then you can invite Seth and change members' roles here.
Next setup step: obtain the website address and server access from Seth, then activate email-and-password sign-in.
What each role can do
- Tester
- Run tasks and submit their own private reports.
- Developer
- Review reports, ask follow-up questions and create practice tasks.
- Admin
- Run their own tests, review reports, and invite and manage testers and developers.
- Super admin
- Admin access, plus granting and removing administrator permissions.
Members
To grant admin permission: open Change access, choose Admin, enter a reason and save. The member must sign in again. Another super admin must change your own access.
Invite a member
Invite participants aged 18 or over using their verified GitLab email. Links expire after 48 hours. Copy the private link and send it yourself; no email is sent automatically.
Invitations
Access history
Mail configuration
Settings stay in Render. Check this server's email readiness and the remaining setup steps.
Invitation email
Open Mail configuration to check this server.
This check reads configuration only. It does not contact the mail server, verify a recipient's inbox or send an email. Private connection values are never displayed here.
Update settings in Render
- Agree the approved sender and SMTP connection with the service owner. Use a host that permits the required mail connection. Render Free service limitations
- Before activating invitation email, have the operator verify a current private backup, apply the reviewed delivery-history upgrade and grant the runtime account access. This page does not upgrade the database.
- Open the web service in Render, choose Environment and enter the approved settings privately. Save and redeploy, then return here to refresh status. This page shows the configuration loaded by the running service.
- With the recipient's approval, create an invitation in the Admin panel and choose Send email. Check its attempt history and confirm actual receipt. A mail-server acceptance alone does not confirm inbox delivery.
SMTP setting names
Keep KICAD_SMTP_ENABLED=false until activation is approved. The other values come from the operator; do not paste secrets into reports or chat.
- Connection
KICAD_SMTP_HOST,KICAD_SMTP_PORT- Encryption
KICAD_SMTP_TLS:starttlsorimplicit- Sender
KICAD_SMTP_FROM- Authentication
KICAD_SMTP_USERNAME,KICAD_SMTP_PASSWORDwhen required- Optional
KICAD_SMTP_CA_FILE,KICAD_SMTP_TIMEOUT_SECONDS
When all prerequisites are approved, the operator can enable email with KICAD_SMTP_ENABLED=true. Invalid enabled settings prevent service startup; correct them in Render.
Community testing
Test workflows
Choose a workflow, follow its steps, and report what happened.
Local practice catalogue
Practice before your first report
Try the reporting process without a KiCad project file. Practice results do not verify a release.
Browse workflows —
Three tester places per roundConnect to load tasks.
Loading sample workflows…
These are sample workflows for demonstrating the website. They do not verify a KiCad release.
Task workspace
Selected workflow
PreviewSelect a workflow
Choose a workflow name to preview its instructions. Previewing does not reserve a place.
No active task
Start a workflow when you’re ready. Your instructions and report form will appear here.
YOUR PARTICIPATION
My activity
Assignments and results saved for your selected tester.
Switching the sample tester changes the activity shown here. Demo identities are for rehearsal; real sign-in is a later milestone.
Loading your activity…
WORKSPACE / NOTIFICATIONS
Notifications
Saved website notifications for your selected identity.
Reminders are created after 12 hours; unfinished assignments release at 24 hours. Choose Demo Developer to rehearse correction alerts. Email delivery is planned.
Connect to check automatic reminder and release scheduling.
Loading notifications…
WORKSPACE / DEVELOPMENT STATUS
Build status
What this test build supports, and what is still needed before release testing.
Complete locally
Run a working backend
The local Python service handles requests and connects to storage. The website uses that service to load tasks and save your actions.
Complete locally
Keep information in a database
Tasks, assignments, reports, screenshots, and conversations are saved together in linked records. Server-restart checks proved that saved tasks and reports remain available.
Local reporting implemented
Report passes and failures
Store version information, an explanation, and a screenshot together. Failures require an explanation and image. Seth's approved workflow and final reporting requirements are still needed.
Local rules implemented
Keep independent attempts and explained history
Three places and one active task remain enforced. Corrections preserve earlier outcomes and evidence, and notify sample developers. Website reminders and automatic release now run locally; email delivery is still planned.
Expanded local demo
Follow the testing process in the browser
Sample developers can add practice tasks through Manage tasks. Testers can browse workflows, submit reports, view evidence and corrections, and follow investigation updates. After submission, choose a related available task or browse all workflows. Wider user testing with approved workflows remains.
Local investigation implemented
Review reports and ask for more information
Sample developers can inspect reports, evidence, and correction history, start an investigation, and ask the reporter a question. The tester can reply privately and follow the review state. Public release progress still needs agreed verification rules.
Local discovery implemented
Find tasks with search and filters
Skip the reporting rehearsal, search task information, filter by skills and task status, and browse six tasks per page. Task details show the build target, OS scope and instruction revision. The real KiCad practice project and build-eligibility rules still need Seth's input.
LIVE CONNECTION
Checking storage…
Waiting for the backend health check.
WebsiteBackendDatabase
NEXT REQUIREMENTS
Prepare the hosted test build
GitLab sign-in and account administration are implemented. Hosted activation still needs a registered GitLab application and an HTTPS address. An approved KiCad workflow, email delivery, GitLab issue links, and release-verification rules remain open.
The progress shown here is development progress. Community release-verification graphs are still planned.
A short walkthrough for Seth
- Choose Demo Developer and use Manage tasks to save a practice task with clear steps and expected behavior.
- Choose a sample tester, read the new task, and start it.
- Select Passed or Failed and enter the KiCad and OS versions. For a failure, explain what differed and attach a screenshot.
- Save the report, review the related-task suggestions, then open My activity to retrieve the report and its evidence.
- Choose another tester to demonstrate independent participation.
- Choose Demo Developer, open Developer review, and ask a follow-up question.
- Return to the report’s tester to reply and see the saved conversation.
DEVELOPER WORKSPACE
Review reports
Investigate independent practice reports and ask their authors for more information.
Choose Demo Developer to use this screen. Reports and conversations are visible to their author and sample developers. Review states do not mark a workflow verified or close an issue.
Choose a developer identity to load reports.
ADMIN WORKSPACE
Manage practice tasks
Add clear instructions for testers to rehearse the process.
Choose Demo Developer to add a task. Saved tasks appear immediately in Browse workflows with three tester places. They are practice tasks for any OS and do not verify a KiCad release. This demo uses sample identities. GitLab sign-in is implemented separately; real workflow publication is still planned.
Saved tasks
Choose a developer identity to manage tasks.