Skip to content

Recommend to opt out hacky tests on the page that is linked in leak tracking error.#246

Closed
polina-c wants to merge 1 commit intomainfrom
polina-c-patch-1
Closed

Recommend to opt out hacky tests on the page that is linked in leak tracking error.#246
polina-c wants to merge 1 commit intomainfrom
polina-c-patch-1

Conversation

@polina-c
Copy link
Copy Markdown
Contributor

No description provided.

instead of in tear down, to allow the cycles to happen.

### 4. The test throws flutter exception
### 4. The test is hacky
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Following up on request from flutter/flutter#154481
IMO, hacky tests should generally be avoided. :)
Does this scenario need to be documented then? It feels like a blank check that anyone could say, well let's just skip testing for leaks since this test is a hack. That feels like a test that is not very valuable.

Copy link
Copy Markdown
Contributor Author

@polina-c polina-c Oct 20, 2024

Choose a reason for hiding this comment

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

Yes, we want to avoid hacky tests as much as possible.
But, some tests have to be hacky.

So I suggest the rule like "To opt out a test, prove carefully that the test is hacky".

But, yes, we can skip documenting this to reduce tendency to opt out tests.

@polina-c polina-c changed the title Update TROUBLESHOOT.md Recommend to opt out hacky tests. Oct 20, 2024
@polina-c polina-c changed the title Recommend to opt out hacky tests. Recommend to opt out hacky tests on the page that is linked in leak tracking error. Oct 20, 2024
@polina-c polina-c closed this Oct 23, 2024
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