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

feat: adding allure integration reports #158

Merged
merged 26 commits into from
Feb 4, 2025

Conversation

FedericoRuzzier
Copy link
Contributor

List of Changes

Adding allure reports

Motivation and Context

Needed in order to show the results of the integration tests

How Has This Been Tested?

Manually

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

- name: Generate allure report
if: ${{ inputs.allure }}
shell: bash
run: |
Copy link
Contributor

Choose a reason for hiding this comment

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

utilizzando docker se falliscono il comando non va in errore, questo vuol dire che non abbiamo mai un fallimento. Il notify alla fine è inutile, dobbiamo andare a controllare il report allure a mano

Copy link

github-actions bot commented Feb 4, 2025

This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

Copy link

sonarqubecloud bot commented Feb 4, 2025

@FedericoRuzzier FedericoRuzzier merged commit 511e26e into main Feb 4, 2025
14 checks passed
@FedericoRuzzier FedericoRuzzier deleted the allure-integration-reports branch February 4, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants