Manual testing
Tools
Manual tests for the Tools panels, the Services tab and the files panel, against a real app in a real sandbox.
Manual tests for the Tools panels, the Services tab and the files panel, against a real app in a real sandbox.
Most panels run a script inside the sandbox, so they need an app to look at. Build one first: “a Laravel app with a tasks table, sign-in, and a page listing tasks”. For Postgres and MySQL checks, ask for a Docker Compose app with that database.
.env (or a compose db service), it connects to that database; with several, the menu at the top left switches between them..env, and the app can read it after a restart..env file adds each line as its own secret.sam@example.com under Shared with you; Stop sharing turns it off in their projects.public/favicon.svg.error -healthcheck, "exact phrase", a OR b) filters them; Live follows new lines.Use a sandbox started from an image built after this change (php artisan sandbox:update moves older ones over).
artisan serve’s request lines with grey timestamps and dots, and slow requests’ times in amber (100ms and up) or red (500ms and up).[32m-style codes show, even during a burst of output.error -favicon, "exact phrase", a OR b) keeps only matching lines and shows how many; clicking one clears the search and highlights it among its neighbours.