Timeline for How to structure unit tests for a GUI app using C# and NUnit
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2012 at 1:50 | comment | added | S.Robins | If your customer specifies a screen should look a certain way, or should change in a certain way, then you should be able to test for these things. Capturing specifications as tests is the heart of the BDD methodology, and I've never found a situation where you couldn't - albeit creatively - find a means to automate a test. The real question is whether the testing will be of value, whether the application is factored well enough to allow you to automate all of the tests in the first place, and whether the tests will be cost effective. I agree though, that sometimes they are not. | |
| Jan 26, 2012 at 9:03 | history | answered | ViSu | CC BY-SA 3.0 |