Hi Bryan!
Thanks for your interest in this idea! It´s maybe something to discuss in the upcoming TechSummit?
Using Innovator to organize Innovator upgrades is an unexpected but great idea! What building technique or application would fit the purpose best?
Requirements Engineering?
Custom application?
I assume this topic is related to manual test cases and not TAF. But of course, TAF users would probably also love to have a set of common test cases.
In general, the tool should be easy to use for the people who have to write the tests.
The official guidelines describe quite well how to organize the test plan. But from my POV, the guide doesn’t contain enough “realistic” examples. And it’s a bit over the top that each step starts with “A. Install Aras Innovator.” [emoticon:0f36700dfeb3494fa10d47dd9e1f90a1]
In my upgrades, the team always showed more than enough common sense to deal with an "imperfect" test plan.
So far I used MS Word, the individual steps looked something like this:
My document contains general tests and specific tests for PE, MPP, code tree mods, custom stuff, etc.
Word is not my favorite format for a test plan. I haven’t done an upgrade in a while.. I wrote these test cases long before a test plan was even a requirement at all. Today I would also include the names of relevant Methods, better (more detailed) description, better English, better images,...
