Tests

Every test run on EDGEwave so far: how to run it again, what to expect, and what it showed. Each phase ends with a hand test by the owner (design, “Phases”); new tests are added here when they are first run.

Last updated 2026-10-16.

At a glance

Automated

Type check, build and unit tests

npm install
npm run typecheck
npm run build
npm test

Expected: no errors, dist/extension.js and dist/editor.js written, and every unit test passing. The Check workflow (.github/workflows/check.yml) runs the same on every push to main that changes code, and on pull requests.

The unit tests are in test/edits.test.ts, over the pure code in src/audio/, src/doc.ts and src/redmod.ts:

Smoke test: VS Code with a stand-in REDcode

npm run build
npm run smoke

Downloads VS Code stable once (cached in %TEMP%\ewsmoke), and runs it at 150% scaling with EDGEwave and a stand-in REDcode (tools/smoke/stub). The stub serves generated tones, so no game or REDbridge is needed: sound 42 (2 s stereo, 440 Hz, event smoke_event) and sound 43 (1.5 s mono, 660 Hz, event smoke_second). The script drives the editor page over the DevTools protocol, including VS Code’s own quick picks and Ctrl+Z, then checks the files written. It writes editor.png and mix.png to %TEMP%\ewsmoke.

To run it from a terminal inside VS Code, unset ELECTRON_RUN_AS_NODE (the script does this for the VS Code it starts). Keep the temp path short: VS Code’s files pass Windows’ 260-character limit otherwise.

Last run 2026-10-16: pass (PASS A1 edits; A2 Add Sound, preset, start, a two-track render; A3 Into the Game, override and REDmod).

Spike: decoding and encoding in VS Code’s webview

Run on 2026-10-15 with a game voice line (Ogg Vorbis, exported by REDbridge) and a game sound effect (Ogg Opus, from sfx_container_1829.opuspak), in a webview of VS Code 1.142.0 (Electron 43.7.7, Chromium 150), with headless Chrome 154 as the control. No game data was kept. The results decided how EDGEwave gets its audio (design, “How it is built”).

The owner’s retest of REDcode’s player found the same on 2026-10-15; REDcode 0.8.0 decodes Opus in the extension and serves WAV.

Hand tests

Before any hand test

Report anything that differs, with the phase and the step number.

A1 Edit

What is built: A1 Edit. Pass (2026-10-16).

1. Start. Run Run EDGEwave with REDcode main (F5) and open a REDcode project in the window that starts.
2. A sound effect. REDcode: Browse Game Sounds, play a sound, click Open in EDGEwave. Expect: a document at source/raw/sfx/<event>/<hash>.edgewave opens in the editor, with the waveform and the format in the header.
3. A voice line. Open a voice .wem from Game Assets in REDcode’s player and click Open in EDGEwave. Expect: its document at its game path under source/raw, Voice line ticked, and Translate and Re-Voice in the header. Clicking either says it is planned.
4. Listen and select. Space plays and stops. Drag on the waveform to select; play then plays the selection; loop loops it. Ctrl+wheel zooms, the wheel scrolls, Fit shows the whole sound.
5. Edit. Try Trim, Cut (Ctrl+X or Delete; what is cut can be pasted), Copy and Paste (Ctrl+C, Ctrl+V at the cursor), Silence, Fade in and out with each curve, Apply gain, Normalize, Mono or Stereo, Set loop. Each appears in Edits; × removes one.
6. Undo and redo. Ctrl+Z and Ctrl+Y (or Edit > Undo) step through the edits; the tab shows unsaved changes; Ctrl+S saves.
7. Render. Pick a sample rate and click Render WAV. Expect: the document is saved, and the WAV beside it plays as edited (open it in REDcode’s player).
8. Reopen. Close the editor and click Open in EDGEwave on the same sound again. Expect: the same document, with its edits.
9. The Sounds view. Click the EDGEwave icon in the activity bar. Expect: the documents from the steps above, each opening in the editor; with none, the Browse Game Sounds and Open Sound… buttons.
10. Fit. Make the editor short (drag the panel up) and narrow. Expect: the waveform shrinks, the panes scroll, nothing runs off the bottom.
11. A file. Right-click a .wav or .ogg in REDcode’s Project view, or in the Explorer, > Open Sound in EDGEwave…. Expect: a document beside it, rendering <name>.edit.wav for a .wav. In the Project view the entry shows on every file (VS Code gives a view’s menu no file extension); on a file that is not a sound it says so.

A2 Mix

What is built: A2 Mix. Retest pending of round 1’s five findings.

1. An A1 document. Open one you made in A1 (the Sounds view). Expect: it opens as one track, with its edits; the Mix bar, one lane and the track controls are above the clip editor.
2. Add Sound. Click the Add Sound icon, type part of an event name (such as gun or door), pick an event and a variation. Expect: a second lane, selected, with its waveform in the clip editor.
3. Add a game file and a file. Add Sound > A game file by its path… (a voice line’s path from Game Assets), and > A sound file…. Expect: a lane each. A voice line’s track has Voice line ticked.
4. Place. Drag a clip along its lane; or type Start. Click an empty part of a lane or the ruler to place the mix cursor. Expect: the lane moves, the mix’s length in the Mix bar follows.
5. Listen. The Mix bar’s play icon (Shift+Space) plays everything from the mix cursor; the Clip bar’s (Space) plays the selected clip through its own effects; stop stops either; loop loops either. The edge icons move the mix cursor to the previous or next start or end of a clip.
6. Track controls. Change Level, Pan and Rate; try Mute and Solo with three tracks. Expect: you hear the change in the mix; muted lanes are dimmed.
7. Effects. Add effects one by one from Add effect…, change their values, untick one to bypass it, remove one with ×. Try each preset on a track and on the master.
8. The radio test (the design’s A2 test). Two game sounds, one with the Radio preset, overlapping. Render WAV. Expect: one WAV that sounds like the mix, reverb tails not cut off.
9. Undo and redo. Ctrl+Z and Ctrl+Y through track moves, effect changes and added tracks.
10. Remove. Remove a track. Expect: its lane goes; Remove is greyed when one track is left.
11. Fit. Make the editor short and narrow. Expect: nothing runs off the bottom; the lanes scroll past four tracks; the panes scroll.

A3 Into the game

What is built, and the research behind the routes: A3 Into the game. Not run yet. Steps 1 and 2 are the design’s A3 test.

Unverified until this test: that the game plays an override, and that REDmod accepts a 48 kHz 16-bit WAV.

1. Override. Open a sound effect from Browse Game Sounds in EDGEwave, change it so you will hear it (reverse a part, or the radio preset), and click Into the Game… > Override this variation. Expect: a message naming the .opuspak written under source/archive.
2. Pack and play. Click Pack (plain archive layout), install with REDcode, and play where the sound happens. Expect: your version.
3. REDmod. On a sound effect with an event name, Into the Game… > Replace the event with REDmod, pick a type. Expect: source/customSounds/<event>.wav and an entry in source/resources/info.json. With redcode.pack.redmod off, the message says so.
4. REDmod in the game. Turn on redcode.pack.redmod, Pack, deploy and play. Expect: your sound for that event. If REDmod’s deploy rejects the WAV, its log (tools/redmod/bin/REDmodLog.txt) says why; send the line.
5. Silence. Silence the event with REDmod on another event. Expect: a mod_skip entry; in the game the event is silent.
6. The last choice. Into the Game again on the same document. Expect: the route you used last is first.
7. A voice line. Into the Game on a voice line’s document. Expect: a message that voice lines cannot go in yet, and only the named REDmod route.