Testing of Interwoven applications..

Markandeyulu

Is there a typical testing procedure that Interwoven developers need to adopt....after the development is done.
Would it be like any other code review & testing that happens with the typical projects ( I am talking of purely templating and nothing else here )...

If so are threre any stadnards i need to follow as part of the testing..?? pls suggest...if there are any..

Adam Stoller

There are no *required* procedures or standards here - it's generally left up to the organization or individual involved.

Ideas that come to mind off the top of my head are:

• If you have a development TeamSite Server as well as a production TeamSite server - do most of your development and testing on the development server first and then bring it over to the production server and re-test / validate.
  
• Limit the accessibility of new templates using the <allowed> alement within templating.cfg and/or using a distinct branch or workarea in which you can try things out without affecting anyone else.
  
• Code reviews are always good ideas - but to be useful here, you'd probably need a sufficient number of other folks who develop templates to do the review - you could probably link this idea into the previous ideas and let other developers not only look at the code but try it out too.

Hope that helps. Others will probably offer additional ideas.

--fish
(Interwoven Senior Technical Consultant)