I am pretty new to TestPartner, and am creating my own project from scratch for the first time. Projects created by others that I've run I've often found to be very confusing (as all the scripts are in one place, you can't easily tell what the hierarchy of scripts is - i.e. which ones should you be running, and which are sub-scripts that will get called).
So does anyone have a good way of actually organising a project for an application - I am playing with different projects, naming conventions etc. but wondered what you guys thought.
The main problems I'm having are, if I organise my scripts into separate projects then I need to duplicate them as you can't call scripts from other projects during execution. But if I have all my test for an app in one whole project...phew! Confusing! Any ideas?
What I generally do is use a naming convention for the sripts. Smoke test scripts start with the word smoke_, ui scripts with ui_, driver scripts with dvr_, etc. That at least sorts the list according to general use of the script.