Rule of thumb - don't blindly trust other people's code. I've used DUnit2 for years to put some quick test cases together to make sure 3rd party code I use, work as advertised. Obviously it is not as thoroughly tested as my own code, but just enough to prove some assumptions.
I guess, the usual ways. Various kinds of automated tests (Unit tests, integration tests etc) as well as the (somewhat more manual) user (developer) IDE tests and installation package tests.
There are scriptable UI testing tools that can compare screenshots to spot visual differences which in theory can help testing visual code - but it is a bit of work to set up the tests, I suppose.
You mean when writing customs components? Or testing forms made with existing components?
ReplyDeleteAsbjørn Heid Yes, I think about custom components. Especially custom visual controls.
ReplyDeleteDefine testing please. There are many forms of testing.
ReplyDeleteShift+F9.
ReplyDeleteBrandon Staggs "It builds, let's ship it?"
ReplyDeleteIt ran once and didn't crash?
ReplyDeleteI have written extension on top of DUnit that allows me to test component packages as part of our automated building process
ReplyDeleteIt looks like it will compile, ship it.
ReplyDeleteRule of thumb - don't blindly trust other people's code. I've used DUnit2 for years to put some quick test cases together to make sure 3rd party code I use, work as advertised. Obviously it is not as thoroughly tested as my own code, but just enough to prove some assumptions.
ReplyDeleteI guess, the usual ways. Various kinds of automated tests (Unit tests, integration tests etc) as well as the (somewhat more manual) user (developer) IDE tests and installation package tests.
ReplyDeleteThere are scriptable UI testing tools that can compare screenshots to spot visual differences which in theory can help testing visual code - but it is a bit of work to set up the tests, I suppose.
ReplyDelete