Hi Daan,
thanks for sharing this guide!
Regarding: 11. Test Everything
"Test everything" is really the perfect term to describe this important task. But what is "everything"? From my POV testing should also involve trivial common tasks like "open Parts, edit Parts, create a new version of Parts, do an ECO, test your TGVs, do this, try that,..." .
Not that we don´t trust Aras regarding testing these general functions, but often small, subtle customizations have an impact in the most unexpected places.
This one reminds me of this thread: link
Why does community not work together to create a generic general test plan that covers most of the essentials that really everybody should check? I wouldn’t make it fully public, but maybe there are people interested in working together?
A quick side story: This thread was the result of a patch upgrade acceptance test. I was actually already finished with the upgrade. Patched all code tree files, merged all Methods,... . It was a perfect run! Speed record! Until a few fatal clicks in the wrong corner. And then a year-long odyssey began. [emoticon:d6dd260102fd406884fc96b8bc59760b]
I'd love to work on a general test plan project. We are working on writing some automated test scripts to help expedite Aras testing. Our environment has a lot of customizations and acceptance testing during each upgrade is painful.
Hi Jamey,
thanks for your interest in this idea!
What do you think would be the best format and platform for a collaboration project like this?
The easiest option would probably be to use shared Google Docs. However, I'm not sure if Word and Excel are really the best formats to work with.
So far I worked with test plan in Word, but I was never fully satisfied with the result.
What I really wanted was a more structured overview - ideally something I could tick off - that links to the individual test plan items. The whole use case is more like Requirements management.
Or maybe even automated test scripts, like you mentioned. Are you working with TAF, or do you use a custom solution?
Side note: I've also seen some people use PowerPoint for their test plans, which ended up looking more like a sales presentation. Let’s please agree not to use PowerPoint. :)
