1. Upgrade Attempt Run Log
Planned
Unknown / Not Finished
Attempt 1: Upgrade Attempt 1 - Initial Odoo.sh Test Upgrade
Source: production
· Target: upgrade-test
· Version: -
· DB: -
First Odoo.sh upgrade attempt using the latest production backup or restored staging copy.
Next action:
Confirm backup, trigger Odoo.sh upgrade test, capture build result, and log all blockers.
2. Test Cycle Tracking
Track technical testing, functional testing, regression testing, UAT, performance review, and go-live rehearsal.
Not Started
Technical Testing
Attempt 1
10. Technical Smoke Test
Confirm upgraded database opens, core menus load, custom modules install/upgrade, server logs are clean, and no critical traceback blocks usage.
Not Started
Functional Testing
Attempt 1
20. Core Functional Test
Validate CRM, Sales, Purchase, Inventory, Accounting, Website, Helpdesk, and any critical client-specific operational flows.
Not Started
Regression Testing
Attempt 1
30. Custom Module Regression Test
Test all uploaded/custom modules affected by scanner findings, dependency risks, XML/view issues, Python API changes, and JavaScript changes.
Not Started
Client UAT
Attempt 1
40. Client UAT Cycle
Client validates daily business workflows, reports, permissions, documents, emails, website flows, and agreed sign-off criteria.
Not Started
Performance Testing
Attempt 1
50. Performance and Log Review
Check response speed, scheduled actions, queue/jobs if applicable, error logs, long-running operations, and database-heavy workflows.
Not Started
Go-Live Dress Rehearsal
Attempt 1
60. Go-Live Dress Rehearsal
Validate final backup, upgrade timing, rollback path, post-upgrade checks, DNS/Odoo.sh branch plan, and communication plan.
3. Create Issue / Blocker
4. Issue Register
Track every blocker, failed test, client UAT issue, scanner issue, and upgrade log problem until resolved or deferred.
No issues logged yet.
How ERPWeb Should Use This Page
Every Odoo.sh upgrade attempt: create or update an attempt, paste the Odoo.sh build URL, capture result, blockers, next action, and lessons learned.
Every testing round: update the matching test cycle with tester, status, evidence, and notes.
Every blocker or failure: create an issue, assign it, link it to the run attempt/test cycle, then move it to Ready for Retest when fixed.