Using Aras to Manage Aras Upgrade Planning, Test Plans, Test Records

“Legal” is an important topic - both for Innovator users and for Aras itself!

I believe nobody really wants to see their own test plan made public. And I don´t think Aras wants that either. I deliberately chose the “Tab Indicator” example above because I´ve already mentioned this feature about a dozen times in the forum anyway.

Please note that we have the following sentence in the terms of use:

"Licensee may not ....disclose, transfer or otherwise make available the results of any performance, capacity or functionality tests or any benchmarking testing of the Licensed Software to any third party."

Therefore, I wouldn´t support a completely open test plan (similar to a GitHub community project). The information should only be available within a closed group. 

In my view, the key point is to have well-designed templates that users can then use to create their own test plans:

Scope

• General tests - What to check after install, basic navigation,...

• Application-specific tests, PE, MPP, etc. E.g. describe what shall happen when you click the "Create new manual revision button" or create a ECO. User often have customized these features. But a test template could cover already 80% of the involved functionality. 

• Examples to show how to describe code customizations

• Templates for partner products, especially those using DLLs

• Templates for commonly used community products (if they represent a feature that is typically used as-is).

• Test Federation and REST API connections. In best case we can create a standard of how to "simulate" these kind of external data.

• ...

It would be very helpful if the Aras Update Team could also provide feedback on this idea - after all, they will ultimately have to work with our "brainchild"