Database JSON field mismatch in test assertions due to missing attribute casting

[idehen-divine]

When testing database assertions with assertDatabaseHas(), JSON fields like variables may cause failures if the attribute is not explicitly cast in the model.

Issue:

Laravel stores JSON as a string, leading to double-encoded values.
This causes assertDatabaseHas() to fail because it expects an exact match.

Steps to Reproduce

Run php artisan test.
The test fails because the JSON field is stored as a string but asserted as an object.

Expected Behavior:

The test should pass because the inserted record matches the expected values, including JSON fields.

Actual Behavior:

The test fails because Laravel stores variables as a string (double-encoded JSON), causing assertDatabaseHas() to look for a mismatched format.

[bhimbho]

the test looks okay to me

[idehen-divine]

@bhimbho the test is not the issue, the issue comes from the model, no cast so it's reading variables as string instead of json

issue:

fix: