testing-erp

Tests Divalto ERP zooms via Playwright browser automation after compilation and SQL sync.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill testing-erp-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-erp
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/testing-erp
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill testing-erp-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After creating or modifying an entity in a Divalto Diva project, developers need to verify that the compiled zoom actually works inside the ERP web interface. Manually logging in, navigating the menu graph, opening zooms, and checking technical metadata is repetitive and error-prone. ## Core Features & Use Cases - Browser-driven ERP interaction: Connects to the Divalto ERP at localhost:8080/LCWeb via Playwright MCP, handling login, tab management, and menu navigation through the flat regroupement graph. - Post-compilation verification (N6): Opens a zoom after compilation and SQL sync, checks title, navigation bar, tabs, and data presence, with structured checkpoints (CP1/CP2/CP3). - Technical coherence validation via F1: Reads the "A propos du Zoom" dialog to compare RecordSQL, SQL table, mask (.dhof), and module (.dhop) against expected generation tokens. - Use Case: After compiling a new "Livre" entity (zoom 9490), ask the assistant to verify the zoom in the ERP; it reconnects the session, navigates Commerce & logistique > Fichiers, opens the zoom, and presents a coherence report. ## Quick Start Ask the assistant to connect to the Divalto ERP and verify that the zoom for your newly compiled entity opens correctly in the menu.

Frequently Asked Questions about testing-erp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a Divalto ERP zoom after compilation?

After compilation with zero errors and SQL sync, close any open ERP session, reconnect via browser_navigate to localhost:8080/LCWeb, then navigate the menu to the zoom. Verify the title, navigation bar, tabs, and data presence, then use F1 to check technical metadata.

How to navigate the Divalto ERP menu with Playwright?

The menu is a flat graph of regroupements, not a nested tree. Click Menu, select a module, then click Page-type entries to deploy sub-groupings until reaching a Zoom or Programme entry, which opens in a new browser tab.

Why does the F1 dialog show an old module version after recompilation?

Compiled objects (.dhof/.dhop) are loaded at ERP session startup. If the ERP was open during recompilation, close it with browser_close and reconnect to load the new binaries before checking F1 metadata.

Does this skill handle ERP login credentials automatically?

No. Credentials are never stored, displayed, or manipulated by the assistant. The user must type their identifier, password, and profile directly into the browser login page before the assistant clicks the connect button.

What is required before using Playwright browser tools with the ERP?

Playwright MCP must be configured in .mcp.json and loaded at session start, and the Divalto ERP must be running at http://localhost:8080/LCWeb. If browser_* tools are unavailable, restart the Claude Code session.