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

Allow retrieving the messages corresponding to a test case #23

Open
lbroudoux opened this issue Jan 7, 2025 · 1 comment
Open

Allow retrieving the messages corresponding to a test case #23

lbroudoux opened this issue Jan 7, 2025 · 1 comment
Assignees
Labels
component/documentation Improvements or additions to documentation component/runtime Runtime behavior of test container keep-open Explicitily keep open kind/enhancement Enhancement of existing feature
Milestone

Comments

@lbroudoux
Copy link
Member

Reason/Context

As of today, we can launch contract tests with the library and get a TestResult object that provides details on global success and also success on each operation. However, we can not easily retrieve the detailed request/response pairs or event messages that were exchanged with the tested endpoint to realize additional checks or get more informations on what's wrong.

Description

We should provide some getMessagesForTestCase(testResultId, testCaseId) and getEventMessagesForTestCase(testResultId, testCaseId) utility methods to retrieve those messages.

Implementation ideas

Those methods could be set directly on MicrocksContainer and call the REST API exposed by Microcks server.

@lbroudoux lbroudoux added component/documentation Improvements or additions to documentation kind/enhancement Enhancement of existing feature component/runtime Runtime behavior of test container labels Jan 7, 2025
@lbroudoux lbroudoux added this to the 0.3.0 milestone Jan 7, 2025
@lbroudoux lbroudoux self-assigned this Jan 7, 2025
Copy link

github-actions bot commented Feb 7, 2025

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale Stale due to inactivity label Feb 7, 2025
@lbroudoux lbroudoux added keep-open Explicitily keep open and removed stale Stale due to inactivity labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/documentation Improvements or additions to documentation component/runtime Runtime behavior of test container keep-open Explicitily keep open kind/enhancement Enhancement of existing feature
Projects
None yet
Development

No branches or pull requests

1 participant