Files
status-go/internal/protocol/sqlite/prepare_migrations_test.go
Igor Sirotin f3e4363808 refactor: move protocol to internal/protocol
Part of the Go project layout migration, item 27.

Pure move plus import-path rewrite across 502 files. No API or behaviour
change. `internal/` keeps the messaging application logic unimportable
from outside the module, which is what the issue asks for -- status-go is
consumed through the C-bindings in mobile/, not as a Go library.

Things that had to follow the move, beyond the Go imports:

- tools/generate-handlers/template.txt. messenger_handlers.go is
  generated, and the template hard-codes the imports it emits, so the
  generated file kept importing protocol/common and failed typecheck.
- .gitignore. The ignore rule for that generated file was pinned to the
  old path; without moving it, a 1486-line generated file starts being
  tracked.
- Makefile: the logosstorage and torrent test targets (both the archive
  packages and ./protocol itself), the archive README, migration-protocol.
- scripts/run_unit_tests.sh, which names the protocol package explicitly
  to shard its tests.
- scripts/cleanup_generated_files.sh and .golangci.yml.

scripts/migration_check.sh also needed a fix that is not specific to this
move: it validated every file the branch touched under a migration dir
against the timestamp naming rule, and a directory rename makes every
migration in it look newly added. It now excludes renames, so moving a
migration is not mistaken for adding one.

refs #7067
2026-08-21 10:11:05 +02:00

57 lines
1.4 KiB
Go

package sqlite
import (
"testing"
"github.com/stretchr/testify/require"
)
func TestPrepareMigrationsEmpty(t *testing.T) {
names, _, err := prepareMigrations(nil)
require.NoError(t, err)
require.Empty(t, names)
}
func TestPrepareMigrationsWithDefaultMigrations(t *testing.T) {
names, _, err := prepareMigrations(defaultMigrations)
require.NoError(t, err)
require.NotEmpty(t, names)
}
func TestPrepareMigrationsErrors(t *testing.T) {
// Two migrations with the same name in the same set.
names, _, err := prepareMigrations([]migrationsWithGetter{
{
Names: []string{"name1.sql", "name1.sql"},
Getter: nil,
},
})
require.EqualError(t, err, "migration with name name1.sql already exists")
require.Empty(t, names)
// Two migrations with the same name in different sets.
names, _, err = prepareMigrations([]migrationsWithGetter{
{
Names: []string{"name2.sql"},
Getter: nil,
},
{
Names: []string{"name2.sql"},
Getter: nil,
},
})
require.EqualError(t, err, "migration with name name2.sql already exists")
require.Empty(t, names)
// No getter for a migration.
_, getter, err := prepareMigrations([]migrationsWithGetter{
{
Names: []string{"name3.sql"},
Getter: nil,
},
})
require.NoError(t, err)
_, err = getter("non-existing-migration.sql")
require.EqualError(t, err, "no migration for name non-existing-migration.sql")
}