Fixed
Status Update
Comments
ma...@google.com <ma...@google.com>
sg...@google.com <sg...@google.com>
ap...@google.com <ap...@google.com> #2
So IIUC, you're looking for something like assertDoesNotExistOrIsNotDisplayed()
.
I think this could be solved by providing matchers to express "exists" and "isDisplayed", so you can write assert(not(isDisplayed()) or not(exists()))
. I'll have to look back in time to see why we didn't provide those matchers in the first place.
na...@google.com <na...@google.com> #3
In the ideal world I would only need to write
`assert(not(isDisplayed())`
as isDisplayed is true when it is displayed. and I want a negation of it. but current IsNotDisplayed() != !isDisplayed() as it fails if the node does not exist. but I don't care why exactly it is not displayed
`assert(not(isDisplayed())`
as isDisplayed is true when it is displayed. and I want a negation of it. but current IsNotDisplayed() != !isDisplayed() as it fails if the node does not exist. but I don't care why exactly it is not displayed
Description
The selectedDateMillis setter is internal. So it isn't possible to overrite the selected date.
More info (my message on issue 231704914 ):
Why is it only possible to set a timestamp initially and not overwrite it afterwards? If I use a date picker dialoge and have a cancel button there, then I do not use the selected date, but as soon as the user opens the picker again, the discarded date is still selected. Or should I always recreate the entire pickerstate, but that can't be it...?