Skip to content

test: Separating class fixtures to allow for more test configuration #182

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

Closed

Conversation

hindleym
Copy link

@hindleym hindleym commented Apr 1, 2025

What was the problem/requirement? (What/Why)

The existing framework deployed and installed the worker agent automatically and I am trying to test different configurations at install.

What was the solution? (How)

By separating some of the fixture configurations, we can setup our instance and worker agent as needed for the test.

What is the impact of this change?

These changes should have no impact on existing tests. Just provides more control over our specific end-to-end tests when needed.

How was this change tested?

Tested these fixtures changes locally, against individual tests and the windows/linux e2e tests

Was this change documented?

No

Is this a breaking change?

No


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@hindleym hindleym requested a review from a team as a code owner April 1, 2025 22:00
Copy link

sonarqubecloud bot commented Apr 1, 2025

Copy link
Contributor

@leongdl leongdl left a comment

Choose a reason for hiding this comment

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

Looks OK to me - do you have an example usage ?

@hindleym
Copy link
Author

hindleym commented Apr 2, 2025

Found a better way to do this without modifying the existing test fixtures

@hindleym hindleym closed this Apr 2, 2025
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