mr-onion

The Toolshop, locally (Phase 41, TFP-179)

Both versions of Testsmith’s Toolshop, run from their own repository under Docker, so a known-bug benchmark has ground truth (the source shows each bug), a control (the clean version) and no dependence on the hosted site’s resets.

Before the first start

Start and stop

.\scripts\toolshop-local\start-toolshop.ps1 -Sprint sprint5-with-bugs   # or -Sprint sprint5
.\scripts\toolshop-local\stop-toolshop.ps1

A start is still one command from PowerShell. Each step inside the distribution is a command of toolshop.sh, which the scripts run with wsl -d Ubuntu.

Timings, measured on this machine (2026-10-27, in WSL):

Before D26 the checkout was a Windows folder mounted into Docker: a first start took 20 to 25 minutes (the clean version’s packages 20, with-bugs’ about 8), and a later start, once it waited for Composer, 14 to 18 minutes for with-bugs (863 to 1,070 s at Gates B to D) and 381 to 391 s for clean.

Addresses

What URL
The app http://localhost:4200 (with-bugs routes by hash, /#/contact; clean by path, /contact, as their hosted sites do)
The API http://localhost:8091
API documentation http://localhost:8091/api/documentation
Database localhost:3306 (MariaDB)

One version at a time

What Mr Onion adds, and why

Testsmith’s files are not changed. Mr Onion adds:

Removed with D26: installing the packages again with COMPOSER_PROCESS_TIMEOUT=0 when compose’s own composer service gave up at Composer’s 300 s process timeout. On the mounted folder a first install took up to 20 minutes; in WSL it takes 15 s. If composer exits without installing them, or fails on any start, the start stops with an error.