We have something similar. Just make another keyword test called Create Service Order with all the little ones under it. Then you can copy the one keyword test around instead of the many.
You can add your KWT tests and Scripts from the other project as existing items to use them. Then you if you cange it in the master project all sub projects that use them will reflect the change.
This works really well actually.
Im not sure what you mean.
Are you suggesting re-adding all of the test items from another project into the current project.
That seems very inefficient.
Also, if I add a test item to the original project, it will not appear in the "master project".
I will have to add it in both places. Correct?
Projects are stand alone and don't have access to each other's tests. cunderw's suggestion is the way to go.
Use Add Existing to put a pointer in the current project to whatever other test you want in there. It will then run in either project but you only have to update the test in the project where the original lives.
See screenshots...
Thanks guys for your replies.
If I have a project "Create Service Order" which has 100 individual Tests that make up the process, that would mean I will have to add these existing tests to every other project in which I want to create a service order.
If I need to add an additional test to the process of creating a service order, I will have to add them in every project.
Sure, I dont have to rewrite the underlying code for the new test each time, but I still have to add the test item to countless projects that require the creation of a service order.
That is not managable.
Looks like I will have to turn my project into a script called "Create Service Order".
And reserve projects only for larger end to end processes.
