Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ISSUE-687 # Persist report and run-log files to an external space after all tests executions#718

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
rkshpanigrahi wants to merge7 commits intoauthorjapps:master
base:master
Choose a base branch
Loading
fromrkshpanigrahi:master

Conversation

@rkshpanigrahi
Copy link

@rkshpanigrahirkshpanigrahi commentedJul 22, 2025
edited
Loading

Persist report to external repo after all tests executions

Fixes Issue:#687

PR Branch
#ADD LINK TO THE PR BRANCH

Motivation and Context

Checklist:

  • New Unit tests were added

    • Covered in existing Unit tests
  • Integration tests were added

    • Covered in existing Integration tests
  • Test names are meaningful

  • Feature manually tested and outcome is successful

  • PR doesn't break any of the earlier features for end users

    • WARNING! This might break one or more earlier earlier features, hence left a comment tagging all reviewrs
  • PR doesn't break the HTML report features directly

    • Yes! I've manually run it locally and seen the HTML reports are generated perfectly fine
    • Yes! I've opened the generated HTML reports from the/target folder and they look fine
  • PR doesn't break any HTML report features indirectly

    • I have not added or amended any dependencies in this PR
    • I have double checked, the new dependency added or removed has not affected the report generation indirectly
    • [] Yes! I've seen the Sample report screenshotshere, and HTML report of the current PR looks simillar.
  • Branch build passed in CI

  • No 'package.*' in the imports

  • Relevant DOcumentation page added or updated with clear instructions and examples for the end user

    • Not applicable. This was only a code refactor change, no functional or behaviourial changes were introduced
  • Http test added tohttp-testing-examples module(if applicable) ?

    • Not applicable. The changes did not affect HTTP automation flow
  • Kafka test added tokafka-testing-examples module(if applicable) ?

    • Not applicable. The changes did not affect Kafka automation flow

@rkshpanigrahirkshpanigrahi changed the titleISSUE-687 # Persist report and run-log files to an external space after all tests executions #687ISSUE-687 # Persist report and run-log files to an external space after all tests executionsJul 22, 2025
@nirmalchandra
Copy link
Collaborator

nirmalchandra commentedJul 23, 2025
edited
Loading

@rkshpanigrahi , Given a CI run now. Lets see how it goes.
Have you tested this feature? Can you attach some evidence to the ticket or here please?

You can check the CI statis here (once they are complete):
https://github.com/authorjapps/zerocode/pull/718/checks

@rkshpanigrahi
Copy link
Author

@nirmalchandra

I have tested this feature by configuring the repository, username, and token in the http-testing modules. Once all tests were executed, the following reports were successfully pushed to the external Git repository:

Repository Configuration:
reports.repo=https://github.com/panigr/zerocode-test-reports
reports.repo.username=panigr
reports.repo.token=

target/zerocode-junit-interactive-fuzzy-search.html
target/zerocode-junit-granular-report.csv
target/logs/.log

I am taking a look into build failure

nirmalchandra reacted with hooray emoji

@nirmalchandra
Copy link
Collaborator

@rkshpanigrahi , Given a CI run again after your fix. Lets see how it goes. 🤞

rkshpanigrahi reacted with thumbs up emoji

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@rkshpanigrahi@nirmalchandra

[8]ページ先頭

©2009-2025 Movatter.jp