![]() |
|
Do you know where your variables are? | |
PerlMonks |
Re^2: (OT) Tracking Issues, Requirements, Testsby cavac (Prior) |
on Apr 10, 2025 at 12:54 UTC ( [id://11164655]=note: print w/replies, xml ) | Need Help?? |
add it to the automated test suite As afoken already said, in big real world applications, you often can only automate a small amount of tests. For my point-of-sales system, about 50% of the issues in the field are usability issues of the UI. And yes, that includes things like "an old lady refusing to wear her glasses and complaining that the text is too small" (so we added scalability to the main UI mask texts and buttons), touch screen gestures getting misinterpreted because the user did do them in the laziest way possible... A lot of UI stuff is very subjective and the results vary from customer to customer and from user to user and from device to device. Yes, one may (and should) write tests for some of those cases, when it is the best financial choice. But in many cases, a trained eye can catch errors in seconds or minute for which you would have to spend weeks writing test software. And you would need to keep spending weeks writing updates to the software for every small UI change, instead of going through a 10 minute checklist manually...
PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my weekly webcomics
In Section
Seekers of Perl Wisdom
|
|