I am just wondering if anyone is using the Test Toolkit in NAV2016/NAV2017! It seems like a no-brainer to use the included test cases for both customer projects and add-on development...
Would like to hear about experiences with development of test cases in customer projects. Is it possible to do without adding too much overhead to the development time?
0
Answers
We had to employee a developer that would write the code to test our customization.
It took a while (few weeks) but now the testing is very easy.
In other words you have to calculate that it will take some time to do it, so there is an overhead.
The test cases can be checked against examples in Excel, as long as you have a standard format for this. Our test team found this very useful.
I hope this helps.
Writing your code first from start to finish and then write your tests is not correct. You'll be biased towards writing your tests to succeed against existing code. You should always start by defining your tests based on requirements. They will fail because your new feature hasn't yet been implemented. Only then should you start writing your actual code and make it pass the tests. That's proper TDD.
Is it worth it when creating standard products? Absolutely.
Is it worth it when writing customer specific customization? That obviously depends on the project and if you can convince your customer of the extra costs.