|Re: Same AUT Definition for multiple Projects / etc. [message #1006607 is a reply to message #1006424]
||Fri, 01 February 2013 07:13
| Alexandra Schladebeck
Registered: July 2009
I'd certainly not recommend playing around in xml - it may work, but there's no guarantee that it won't do something nasty (and, in the next version, the xml files won't be as readable either).
There's no concept for sharing AUTs or object mapping across projects - but I'm not 100% sure that you need that. It sound like you may need a structure that looks like this:
- PRODUCTIVE TEST (your deliverable)
-- Contains all Use Cases for release
- INCUBATION TEST (your bleeding edge)
-- Contains Use Cases that are in progress
All necessary Test Cases for the project (possible separated into a reusable "library" project and a project that builds on that. The reusable library project should ideally be at an abstract / generic level where no mapping is required - mapping is on a per project basis, and you don't want to have to do it twice.)
If your Test Cases will have to change to accommodate the bleeding edge features, then another way would be to version the project:
Version 1.0 contains Deliverable Test Cases from release 1.0
"Create New Version" copies this project under a new version number.
Version 1.1 can contain the changes necessary for the upcoming release, and version 1.0 remains as a maintenance version to be run against release 1.0.
The two projects are then separate, so if your maintenance version requires test changes that are also necessary in the new version, then those have to be done twice.... which isn't ideal if that happens a lot, but acceptable if it doesn't (in my experience the latter is true, but that doesn't mean it is always the case).
Hope that's useful!
Powered by FUDForum
. Page generated in 0.01453 seconds