Write tests. Not too many. Mostly integration

Re:Write tests. Not too many. Mostly integration by pjmlp on Friday October 27, 2017 @04:46AM (#15566700)

Because there isn't proper way to write unit tests for GUIs for example.

They can only test parts of its behavior, not everything, and are too brittle to any simple UI/UX change.

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration by mbrock on Friday October 27, 2017 @07:45AM (#15567462)

Why not just mock the UI drawing library? (I find this a very interesting question.)

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration by pjmlp on Friday October 27, 2017 @09:39AM (#15568111)

Because you would be implementing a 100% of the UI features and still cannot prove if it meets the UI/UX design specs.

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration by mbrock on Friday October 27, 2017 @11:00AM (#15569014)

I think a lot of that is just the poverty of UI APIs and especially the imperative drawing paradigm. There's no reason in principle why we can't programmatically verify that the basics of the UI spec are fulfilled. If the whole UI layer is just impossible to verify then if we're at all serious about correctness then we should (hyperbolically) stop making UIs until we figure it out.

[ Parent | on HN ]

Re:Write tests. Not too many. Mostly integration by hinkley on Friday October 27, 2017 @01:06PM (#15570237)

I can’t help but think this is because nobody writes testable GUI frameworks. You can’t build a castle on a swamp, unless you’re Monty Python.

[ Parent | on HN ]