2 ms·
> When I'm forced to. I hear you. And I think this may account for some of your frontend testing solutions. (Which I in now way mean to disparage.) Given a se
by eyelidlessness 7y ago
> When I'm forced to.
I hear you. And I think this may account for some of your frontend testing solutions. (Which I in now way mean to disparage.)
Given a set of technologies that allow it, another way is possible, significantly easier, with a faster red-green cycle and probably a higher degree of confidence. It looks a lot like what Gary described in TFA. Given:
- A good type system
- A component system with single-direction data flow
- A state abstraction that is testable outside of the DOM
(Edit: not sure why HN won't let me make a list without empty lines but there you go)
In quite a lot of cases the tests can be isolated to your state logic, and the mere presence of a component and a passing compilation is enough to ensure your frontend works. You can even, with some effort, ensure the presence with the type system.
It doesn't necessarily eliminate all end to end testing scenarios, but for a lot of sites/apps it may.
- steveklabnik 7y ago> (Edit: not sure why HN won't let me make a list without empty lines but there you go) because hn formatting doesn't actually have a "list" concept https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
- eyelidlessness 7y agoIt's not so much that I want it to render as a list (e.g. like Markdown), but that I want to produce separate lines of text without an additional blank line between them.