| || |
I still can't believe that TestPartner doesn't have this functionality… but I'm hoping you guys can tell me different.
Can assets (specifically Modules), be shared across projects? From what I've read so far, we're forced to put everything under the Common project. But that leaves the module open to anyone just screwing up the code.
We're planning on rolling out TP soon to a few dozen script writers. I have about 60 functions already written… but I'm afraid of chaos ensuing on my poor unprotected modules.
I'm just a paranoid VB developer in denial that it can't be done. Just trying to do a little CYA… [img]images/icons/smile.gif[/img]
Re: Sharing assets...
Put them in the Common project, but make everyones access to the common project (That you don't want in there) Read only.
Project A can call functions in modules of Project A or Common.