assertIsNotDisplayed shoudn't crash on a not composed node [305906909]

Assigned

Bug

Status Update

No update yet.

Description

an...@google.com

created issue #1

Oct 17, 2023 10:39AM

It is hard to assert that node is not visible for any reason. In my use case I don't care for what reason the node is not displayed. Either it is because the node is not composed at all, or it was composed, but wasn't placed. This behaviour in LazyColumn is not guaranteed as prefetching can decide to precompose an item in advance. But currently we have

assertIsNotDisplayed() which is crashing if the node is not composed
assertDoesNotExist() which is crashing if the node composed, but not placed And there is no way to write it on my own because fetchSemanticsNode with boolean is internal

Comments

rh...@gmail.com <rh...@gmail.com> #2Oct 18, 2023 08:16PM

I believe this a dup of 187188981, which is fixed but waiting for a release - https://issuetracker.google.com/issues/187188981#comment20

Message last modified on Oct 18, 2023 08:17PM

an...@google.com <an...@google.com> #3Oct 19, 2023 11:57AM

It is not. There we only started filtering out nodes which are deactivated (in a reuse pool of lazy column). In this bug we will also make sure assertIsNotDisplayed() is not creased on a node which doesn't exist

Issue 305906909

Description

Issue summary

Comments

rh...@gmail.com <rh...@gmail.com> #2Oct 18, 2023 08:16PM

an...@google.com <an...@google.com> #3Oct 19, 2023 11:57AM

Add comment

Issue metadata