A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
@Niklas_L
@chaugstvedt Yes, but this would only ensure
visual aspects of your app, and I think you would spend a lot of time defining
good sample data. It's also not strictly a unit test if you have to ensure
rendering of two components does not break the UI.
@Niklas_L
@chaugstvedt I recently added e2e tests to a
frontend app, and it helps to uncover issues with async fetching of data (e.g.
data not loaded as expected after change). You will only discover this in e2e
tests.
@Niklas_L
@chaugstvedt So, Im trying to find a
screenshot, but I have recently used a mobile app, with a textarea and a submit
button below that. Once you click into the textarea, the Android keyboard
overlaps the submit button, and you weren't able to hide the keyboard without
navigating away.
@Niklas_L
@chaugstvedt Here of course, CSS and
component unit tests would not detect that.
@Niklas_L
@chaugstvedt I think this is a good example.
A lot of events are working together against each other ... some are even
out-of-DOM events (browser autofill behaviour).