status-go/static/test-0.132.0-account
Sale Djenic b16a38408a tests: migration test fixed
An issue was that in the `0.97.3` version we didn't have `key_uid` column, later
it was added but there was no chance to set in `key_uid` value properly during
migration and we left it empty. Now in `accounts_and_keycards_improvements.up.sql`
script a constraint `CHECK (length(trim(key_uid)) > 0)` is set for `key_uid` column and
because of it migration test couldn't pass cause `key_uid` was empty.

How it is fixed: the same test account is used but just `key_uid` was added to table to
make migration tests pass again and stored Status test account data refer to `0.132.0`
version.
2023-05-25 19:46:47 +02:00
..
keystore tests: migration test fixed 2023-05-25 19:46:47 +02:00
0x7c46c8f6f059ab72d524f2a6d356904db30bb0392636172ab3929a6bd2220f84.db tests: migration test fixed 2023-05-25 19:46:47 +02:00
README.md tests: migration test fixed 2023-05-25 19:46:47 +02:00
accounts.sql tests: migration test fixed 2023-05-25 19:46:47 +02:00
accounts.sql-shm tests: migration test fixed 2023-05-25 19:46:47 +02:00
accounts.sql-wal tests: migration test fixed 2023-05-25 19:46:47 +02:00
geth.log tests: migration test fixed 2023-05-25 19:46:47 +02:00

README.md

Test account data

Only used for determining if we can login with older status-go accounts in the latest version of status-go