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]
Hi Angela,
Thank you for the elaborate response. You are right that 'Test Everything' is quite vague. You are also right that to us this would include all types of trivial work like checking forms, checking user permissions, testing (admin) menu's etc.
Nice idea to come up with a community 'standardized' outline. I think it will help others a lot as well as the Aras Upgrade team themselves. If you know any more people that could provide input, perhaps we can bring people together?
Best regards,
Daan
P.S. Always fun to read you have been through similar questions before. To me that means there must be many others that are still lurking on the forums.
