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

[Improvement] Publish testing framework #3691

Open
Sopor10 opened this issue Sep 14, 2023 · 6 comments
Open

[Improvement] Publish testing framework #3691

Sopor10 opened this issue Sep 14, 2023 · 6 comments

Comments

@Sopor10
Copy link

Sopor10 commented Sep 14, 2023

Is your improvement request related to a problem? Please describe.

I would like to document our gitversion configuration with tests.

Therefor I looked at your awesome integration tests and wanted to write specific ones for my use case.
They work fine inside the GitVersion repository but at the moment I need to copy a bunch of source code (e.g. LibGit2Sharp) into my repository, as it is not published inside a nuget package.

Detailed Description

I want to use the tests as a living documentation and safty net for the versioning of that repository.
It would be really nice to be able to have some sort of framework for that.

Possible Implementation

It would be really nice, if you would publish all packages to create integration tests for custom gitversion configurations.

@HHobeck
Copy link
Contributor

HHobeck commented Sep 29, 2023

To understand your request: Do you think a change of the existing code is necessary as well (change classes from internal to public) or is it just to publish the existing test framework via nuget?

@Sopor10
Copy link
Author

Sopor10 commented Oct 25, 2023

Sorry for the late reply.
I did not use internal classes, that would need to be made public.

Copy link

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Jan 23, 2024
@arturcic
Copy link
Member

To be honest I don't think we need to publish the GitVersion.Testing project, as it will require maintaining it and it is the only time we got this request. So I would say we do not plan to do that. Sorry about that.

@arturcic arturcic closed this as not planned Won't fix, can't repro, duplicate, stale Feb 19, 2024
@arturcic arturcic reopened this Feb 19, 2024
@arturcic
Copy link
Member

I think there might be a use case for this, when filling failed tests

@arturcic arturcic removed the stale label Feb 19, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label May 20, 2024
@arturcic arturcic removed the stale label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants