Let's assume your developer is reasonably smart. :-)
In that case, he is probably not saying you can't write tests of a Gui
- obviously you can - the question is whether they are unit tests or
not.
In his favor, hardly anyone who claims to write Gui unit tests does
so. What they do is to drive the entire application through the Gui.
That's not a unit test.
I'm a big advocate of unit-testing the Gui in apps where it's
critical. Think medical equipment software, where medical techs use
what the gui is telling them to decide where to cut or where to aim
the radiation!
In such a case, we need to know that the Gui works. And whenever we
_really_ need to know that something works, we need to test it.
A true unit test of the Gui has to replace the entire back end with a
test double of some kind. This is a lot of work. So, while you
definitely can unit-test the Gui and definitely should do it in
safety-critical situations, it's usually not worth the effort in
typical business applications.
> --
> You received this message because you are subscribed to the Google Groups
> "NUnit-Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
nunit-discus...@googlegroups.com.
> To post to this group, send email to
nunit-...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/nunit-discuss.
> For more options, visit
https://groups.google.com/d/optout.