NextERP Documentation
ROEN

Working with NextERP · Article 02

Runboat — the test environment

Applies to Odoo 19 · 20

Runboat automatically builds a test Odoo instance for each branch and pull request in the NextERP code. Each instance is a separate copy: what you do there does not affect production, and parallel tests do not interfere with each other. We use it for:

  • Testing features — changes in the NextERP code, custom integrations, migration scenarios.
  • Task acceptance — before a change reaches production (see "Project Workflow").
  • Reproducing bugs reported through Helpdesk (see "Support procedure").

For projects hosted on odoo.sh, testing is done in the odoo.sh staging branches, not on runboat.

🔗 Access

Runboat replaces the old runbot.nexterp.ro, whose links no longer work. The instances run on NextERP infrastructure and nothing is installed on your computer.

🔑 Login

Open https://runboat.nexterp.ro and click Autentifică-te (log in) in the top-right corner. You receive the username and password from us; the password is sent separately, never in the same email as the address.

After logging in you see only your projects. You log in only once: the instances then open directly, without asking for the password again. The ieși (log out) button next to your name closes the session.

🧭 Main page

Projects are grouped in the left-hand menu. For each project, the list of instances appears, most recent first; older ones are collapsed under it, so that the list stays easy to read.

Each row shows:

  • the status — started: the instance is running and can be opened; stopped: it is available but stopped so it does not use resources; failed: the build did not succeed
  • the branch and code version it was built from

⚙️ Actions per instance

  • Odoo — opens the instance
  • mail — the emails the instance would have sent (captured, not actually delivered)
  • log — the technical log, useful when you report a problem to us
  • pornește (start) — starts a stopped instance; wait a few tens of seconds. The instance stops by itself after a while if it is not used.

🗄️ What the instance contains

For customer projects, the data is a copy of the production database, as of the last refresh, which we do periodically. It is not live data: changes in production do not appear here automatically.

The administrator account is admin, with password admin.

The instances are isolated from the outside world, on purpose:

  • they do not send emails — any message is visible only under mail, so nothing goes out to your customers or suppliers
  • they do not run automated actions — recurring invoicing, synchronisations, scheduled notifications
  • they do not connect to the bank, ANAF (the Romanian tax administration) or payment providers

📋 Keep in mind

  • When you report a problem to us, send the address from the browser bar: it identifies exactly the code version of the instance. If the instance is failed or does not start, also send the link from log.
  • Instances are temporary: as new versions appear, the old ones are deleted, and any change disappears on rebuild. Do not keep anything you care about there.
  • Access is personal. Do not pass on your password; if someone else in your team needs it, tell us and we will create an account for them.
  • Problems with runboat itself (not with the code being tested) are reported directly to the NextERP team, not through Helpdesk.
Documentation by the NextERP team.