Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Integration tests against Firebolt 2.0 #51

Merged
merged 6 commits into from
Jul 29, 2024
Merged

Conversation

stepansergeevitch
Copy link
Collaborator

Added

  • integration testing action for firebolt 2.0
  • test failures reporting

@stepansergeevitch stepansergeevitch self-assigned this Jul 29, 2024
@stepansergeevitch stepansergeevitch requested a review from a team as a code owner July 29, 2024 07:20
@stepansergeevitch
Copy link
Collaborator Author

Copy link
Collaborator

@ptiurin ptiurin left a comment

Choose a reason for hiding this comment

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

minor suggestions, otherwise lgtm

firebolt-client-secret: ${{ secrets.FIREBOLT_CLIENT_SECRET_STG_NEW_IDN }}
account: ${{ vars.FIREBOLT_ACCOUNT }}
api-endpoint: "api.staging.firebolt.io"
instance-type: "M"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we actually need an M-sized engine for metabase testing?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I had some issues where engine reported lack of memory in some cases. That's why I had to update the engine size

Comment on lines +77 to +86
- name: Publish Test Report (JUnit)
uses: dorny/test-reporter@v1
if: failure()
with:
path: 'target/junit/**/*_test.xml'
name: Firebolt 2.0 Metabase driver JUnit Test Report
reporter: java-junit
list-suites: failed
list-tests: failed
fail-on-error: false
Copy link
Collaborator

Choose a reason for hiding this comment

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

We can probably replace it with Allure later on, since it supports JUnit. This way we'll have the reporting standardised across Ecosystem. Let's file a ticket so we don't forget.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Sure, sounds good

@stepansergeevitch stepansergeevitch merged commit 4df043e into develop Jul 29, 2024
2 checks passed
@stepansergeevitch stepansergeevitch deleted the ci-2.0 branch July 29, 2024 12:49
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.

2 participants