| || |
Organization of scripts - library shared by tests
We've just begun the (nightmarish) journey of automating testing on an application that uses a plug in architecture.
We would like to separate tests for each of those plugins into separate test projects under a single test suite. The problem we have run into is that we would like to have some procedures and functions shared between those projects. Things like Login/Logout, Menu Selection and so on are all going to be necessary in all of the sub-projects.
Is there a way to call script outside of the current project or maybe in another project? We attempted to use something like "uses ..\utils\lib" but TC didn't like it much.
Re: Organization of scripts - library shared by tests
Of course, after searching and posting this message, I notice that someone else already asked a similar question just a bit before.
If a forum leader finds this before someone else posts, please remove this topic?