Forum Discussion
While developing, if you find yourself writing code that does the same thing, then it's ideal to make it as a function and reuse it. Also, don't make the functions complicated, break it down into sections if you can.
If the name of your application that you are testing is called "spkpro", then it's not necessary to name all if your function or projects, appending with "_spkpro".
My Project Suite is called "Asset Liability Suite", within this suite, I have many projects which tests different areas of the tool and are named appropriately (which doesn't include the project suite name). Before each tests are run, I import data into the DB; launch the browser; goto the URL; and login into the application. Tests are executed. Finally, perform a clean-up to get the DB back to it's original state.
The actions shown in Italics, are functions that are performed all the time before/after tests are executed. These are all stored in a Common project, which can then be used within the project suite.