Common: Automate testing

[seclerp]

Currently, it's hard to determine if everything is OK with release without making at least manual smoke testing. Let's introduce a set of automated tests to introduce more robust CI checks before release.

Items highlighted with bold font are the most important to cover with tests.

Progress

Frontend tests

• Test data
  • [ ] Prepare test solution(s)
• Integration tests
  • [ ] AddMigrationDialogWrapper
  • [ ] RemoveLastMigrationDialogWrapper
  • [ ] GenerateScriptDialogWrapper
  • [ ] UpdateDatabaseDialogWrapper
  • [ ] DropDatabaseDialogWrapper
  • [ ] ScaffoldDbContextDialogWrapper
  • [ ] CommandPreviewDialogWrapper
  • [ ] CommonDialogWrapper
  • [ ] AppSettingsConnectionProvider
  • [ ] DataGripConnectionProvider
  • [ ] UserSecretsConnectionProvider
  • [ ] PreferredProjectsManager
  • [ ] DialogsStateService

Implementation notes

• Integration tests could use a data from real solution and project environment but should not change or mutate it

[seclerp]

Integration test cases

Add Migration

Positive

• Create a new migration with a valid name when the migration list is empty, should create migration
• Create a new migration with a valid name when the migration list is not empty, should create migration
• Create a new migration with a default name when the migration list is empty, should create migration, the name should be "Initial"
• Create a new migration with a default name when the migration list is not empty, the name should be ""
• Create a new migration with a valid migrations folder, should create migration there

  Negative

• Create a new migration with an invalid name, should fail validation

TBD