In many NAV projects the testing procedure is limited to a minimum and relatively dependent on user acceptance test. It is even not unheard off that a quickly tested NAV solution is placed in the production environment, and if for some reason there are errors, the modifications are just rolled back.
For larger end-user solutions and ISV partners building larger standard solutions for NAV this hands-on way of testing is not viable as they risk spending too much time testing. With an ever growing number of companies running NAV in a multi tenant environment, it is clear that there is a growing need for better testing methods.
In the case of an NAV installation, the issue seems to be that many of the best testing practices that we see from other development projects are either not used by the partner or avoided because the customers have budgetary restraints.