Skip to content

Conversation

@mazin-s
Copy link
Contributor

@mazin-s mazin-s commented Aug 17, 2023

What this PR does / why we need it:

  • Refactoring for easily onboarding future database engine tests
  • Postgres & MSSQL testing.

How Has This Been Tested?:

  • 4 tests are being run.
  • PostGres -> provisioning, app connectivity
  • MSSQL -> provsiioning, and app connectivity.
    -- app connectivity for MSSQL failing. This is not a code issue, rather a pod/image issue. I'm investigating this now.

tests-ran
pg-si_test.log
mssql_test.log

@mazin-s mazin-s self-assigned this Aug 17, 2023
@mazin-s mazin-s requested a review from akshmish August 17, 2023 21:30
@mazin-s mazin-s marked this pull request as ready for review August 23, 2023 17:17
Copy link
Contributor

@manavrajvanshi manavrajvanshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comments and a question:
Why do we have 2 pg - si tests? Can we combine those into one?

Also, what do you think about moving the files appConnectivity.go, provisioning.go and setup.go into a commons folder?


// Nil check
if st == nil || clientset == nil || v1alpha1ClientSet == nil {
errMsg := "Error: ProvisioningTestSetup() starting ended! "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use a better statement here instead of starting ended?
Perhaps something like nil parameters/arguments or initialization failed etc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants