Thanks Trent. I suspected this was a bit unusual, I was just hoping there wasn’t a panic response of “don’t do it!” I’ll let you know if I have any problems but so far it has worked flawlessly.To see my problem just try to make a unit test from Visual Studio to test if a form’s text box is bound to a business object property field. You’ll see that you are blocked in about 12 ways from getting to that screen and property. My method makes it so, as the developers are doing their normal TDD on the business objects, they can reach out to the UI and check that their screens are hooked up correctly too.
We are using the security and localization and having the ability to ensure that every property is set, every control is localized and everything is secure before it goes to our QA department is an incredible time saver.
We have an old copy of Automated QA but I didn’t want to get into the complexity of automation scripts and introduce another application everyone needs to learn. Does the current version of Automated QA let you test such things as localization keys and security settings? Or, do you have make scripts that test “if it was set right, then this would be true” type tests.