Good article about applying test automation on legacy system. Sounds familiar as it is quite complex to write automated tests for existing NAV solutions. An article which translates this article to a Microsoft Dynamics NAV scenario would be nice.
Within one of the LinkedIn groups (sorry, you need to be a member of the “QA Automation Architect” group to be able to read it fully) we started talking about the difference the state of project or product can make for test automation. In this post I will make a distinction between 2 states: new where no code has been written yet and existing where application code has been written, but no test automation has been implemented.
So when creating a totally new product, life for the testers can be made easier by design, that at least is the thought. This does imply that testers, and not just the “manual” testers but all testers, including automation testers if these are a separate breed as some people seem to think, need to actively participate in the requirements phase of a product. With actively participating I do not mean…
View original post 912 more words