-
Notifications
You must be signed in to change notification settings - Fork 251
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
Ensure test cases are independent #72
Comments
/help |
@ahg-g: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Let me work on this issue! |
Seems like TestCacheCapacityOperations does not exist anyomre? |
It's now |
Looks like the issue with TestCacheCapacityOperations (TestCacheClusterQueueOperations) was already resolved in #133 🙂 Looking into the scheduler integration test |
I found the problem with the scheduler integration tests was resolved in #90 |
/reopen |
@tenzen-y: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In an effort to get a binary that "works", we wrote some tests where a test case depends on the state left by previous test cases.
This is problematic for debugging problems and it tends to lead to a lot of test changes when there is a behavior change or you want to insert a case in the middle of the existing ones.
Places that I'm aware of:
And there are similar situations in the following, but it's more like a single complex test case in each:
/priority backlog
The text was updated successfully, but these errors were encountered: