| || |
Testing Navision with Testpartner automation
Does anyone out there have any experience testing MS Navision applications using TestPartner?
Sadly I've not been able to find anything in the Archives (only 2 posts evn mention Navision!) but as TP is the only automation app which supports Navision, hopefully someone else has used it for that purpose!
I'd be interested in any helpful hints on what to particularly look out for; eg:
- which object properties to include in object recognition so that we don't cause ourselves problems later when we merge a new base version from MBS?
- Useful scripts we ought to create first to help life later?
- How modular can we make scripts without causing extra overhead for very little gain?
- Which traps should we be careful to avoid, so we don't end up really needing to throw away the first months work and start again!?!
Thanks in advance for any help.