Ruslan Hrabovyi
Ruslan Hrabovyi
> Could I add a flag to opt out of maxlength checking? I think opting out the `maxlength` only is not enough. We should probably avoid mutating the `element.value`, and...
just wondering if it's reasonable to test this "type-in despite `maxlength`" use case via `triggerKeyEvent`s instead?
I participated in adding a hard error for the `fillIn` and `typeIn`, and I'm sorry to hear it causes issues for you! Let me help to figure it out please....
Thank you for the explanation! Yes, I can see how a manual mix of the `typeIn(` and `triggerKeyEvent(`s can become cumbersome for your use case. In my opinion, we should...
have you tried named import: ``` import { tab } from '@ember/test-helpers'; ``` ?
May you provide with a minimal reproduction? otherwise it'd be impossible to reason about the issue.
> Asserting for an element's attribute does not guarantee lack of behavior on click. I don't think there is a legit way to trigger `click` event handler over a `disabled`...
> This "guarantee" is not part of any spec that I'm aware of. I think this is something, that works for ages in all broswers. See https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/disabled > The Boolean...
> When a user clicks a disabled button, the app does not crash, so the behavior of a test diverges from real life. IMO, the tests and real user are...
> You program your test to click **every** toggle before asserting the result. "Every" in tests sounds suspicuos to me. Often it may lead to fragility, cause if some new...