wevehiculegen2-as-simulator

Validates DM68 AS announcements in the wevehiculegen2 simulator through in-app browser testing.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/alex-jordan547/agent-setup --skill wevehiculegen2-as-simulator-alex-jordan547
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wevehiculegen2-as-simulator
Source: https://github.com/alex-jordan547/agent-setup/tree/main/archive/wevehiculegen2-as-simulator
Command: npx skills add https://github.com/alex-jordan547/agent-setup --skill wevehiculegen2-as-simulator-alex-jordan547

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing audio announcement (AS) behavior in the wevehiculegen2 DM68 simulator is error-prone when relying only on unit tests, e2e scripts, or code reading, which cannot prove real runtime behavior. This Skill enforces manual in-app browser validation so MP3/TTS playback, multilingual output, loops, and terminus states are verified in the actual application flow. ## Core Features & Use Cases - Mandatory Browser Validation: Runs tests in the in-app browser at http://localhost:8080/#/simulateur instead of substituting shell, curl, or e2e evidence. - AS Object Checklist: Covers AS_ARRET, AS_PROCHAINARRET, AS_CONNEXION, AS_DEPART, and related objects, including terminus and sortie d'arret states. - Audio & Language Rules: Verifies MP3 file paths, TTS fallback, IVVSceneMultilingueIgnoreeAS behavior, and loop pause sources like TempsPauseAS. - Use Case: When debugging a multilingual MP3 announcement that falls back to TTS incorrectly, follow the workflow to confirm the composition contains the target AS object, prepare fake .mp3 files under core/bibmm, and record the exact AS output observed in the browser. ## Quick Start Open the simulator at http://localhost:8080/#/simulateur in the in-app browser and validate the target AS announcement by running the composition and recording the exact audio output.

Frequently Asked Questions about wevehiculegen2-as-simulator

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

FAQPage Schema
How do I test AS announcements in the wevehiculegen2 simulator?

Open the simulator in the in-app browser at http://localhost:8080/#/simulateur, add the page containing the target AS object to the composition, set the correct vehicle state, and run the simulation. Record the exact AS text or file sequence the UI produces.

How do I test MP3 audio announcements with fake files?

Fake .mp3 files are valid when the test only needs file existence. Place them under core/bibmm with filenames and paths matching the SAE data, then run the simulation to verify MP3 playback versus TTS fallback.

Can e2e or unit tests replace browser validation for the simulator?

No. Browser in-app testing is mandatory because unit tests, e2e scripts, and code reading cannot prove real simulator runtime behavior. The two evidence types answer different questions and must not be mixed.

Why does a multilingual announcement fall back to TTS instead of playing MP3?

For combined announcements, one missing required MP3 file normally forces a complete TTS fallback rather than partial MP3 playback. Also check IVVSceneMultilingueIgnoreeAS, which silences extra languages for affected AS objects when true.

What vehicle state should I use for terminus announcement testing?

The useful position for terminus cases is often the segment before terminus or sortie d'arret, not at terminus itself. Testing the wrong vehicle state is a common mistake that produces misleading results.