You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I ran into a bit of a gotcha today with testing multiple date-pickers. This is probably because I've been doing something wrong!
Basically my tests for a component with multiple date pickers didn't close the date picker between selecting dates on two different inputs. This worked fine in Ember 3.8, but when upgrading to Ember 3.12 it doesn't. The solution was to close the date picker after choosing the first date and before selecting the second date.
As I say, not really a bug with this addon because it makes sense that actually I should have closed the datepicker originally. But it made me think of two things...
Firstly, maybe the readme should be clear about this? I.e. say that the datepicker needs to be closed if testing with multiple dates? If so, I can do a PR to add that.
Is it worth having a test helper that does these three steps in one helper? Say it was called fillInDate (not bothered about the name), then the above code could be re-written to:
So I ran into a bit of a gotcha today with testing multiple date-pickers. This is probably because I've been doing something wrong!
Basically my tests for a component with multiple date pickers didn't close the date picker between selecting dates on two different inputs. This worked fine in Ember 3.8, but when upgrading to Ember 3.12 it doesn't. The solution was to close the date picker after choosing the first date and before selecting the second date.
As I say, not really a bug with this addon because it makes sense that actually I should have closed the datepicker originally. But it made me think of two things...
Firstly, maybe the readme should be clear about this? I.e. say that the datepicker needs to be closed if testing with multiple dates? If so, I can do a PR to add that.
Secondly, a lot of my tests now look like this:
Is it worth having a test helper that does these three steps in one helper? Say it was called
fillInDate
(not bothered about the name), then the above code could be re-written to:Just an idea, I'm happy to do a PR if you think something like that would be worth adding.
The text was updated successfully, but these errors were encountered: