> But they will notice if some test data they input themselves doesn't give the right answer, or if some minor UI element they never really thought through doesn't seem to work the way they like.
Those people are going to not stop at one; so you will be foolish if you don't write a regression test for the behavior they wanted.
When they find the next thing they think is broken, and you try to fix it, you could regress your earlier fix for the first item.
In reacting to the user reports, you may be breaking other things that are not tested, but at least you pin down the behavior that the users are reporting.
UI element not working right in some way could be a genuine "pass" for testing. I mean, writing some monkey test that feeds events into a UI to check that it's in exactly some expected state could be a big waste of time.
Probably if you were writing a reusable widget framework, you might want that sort of testing, because you could make an inadvertant change which makes every instance of some widget behave differently in downstream applications.
If you have some complex behavior in your UI that doesn't come from the underlying widgets, and has to be right in certain ways, then that could be worth testing.
Those people are going to not stop at one; so you will be foolish if you don't write a regression test for the behavior they wanted.
When they find the next thing they think is broken, and you try to fix it, you could regress your earlier fix for the first item.
In reacting to the user reports, you may be breaking other things that are not tested, but at least you pin down the behavior that the users are reporting.
UI element not working right in some way could be a genuine "pass" for testing. I mean, writing some monkey test that feeds events into a UI to check that it's in exactly some expected state could be a big waste of time.
Probably if you were writing a reusable widget framework, you might want that sort of testing, because you could make an inadvertant change which makes every instance of some widget behave differently in downstream applications.
If you have some complex behavior in your UI that doesn't come from the underlying widgets, and has to be right in certain ways, then that could be worth testing.