| || |
Project/Script best practices
I'm coming from QTP/Winrunner to TC, learning the TC IDE and a few basic questions. My harness in QTP was organized by scripts and function libraries. For example, the folder structure was something like this:
Test Suites - Contained my scripts for specific parts of my web application, like Login for example
Navigation functions - These were navigation functions that got me to a specific place in the web application
Common Functions - Functions I used for common operations, like creating a random user, or clicking on buttons common throughout the web application
Exception handling - Contained exception handling functions
Data Tables - Contained excel tables used in my tests.
And I had a driver that could drive all scripts or only the one's I wanted
All of these was handled by calling the appropriate function subroutine (QTP uses VBScript)
In the concept of Projects in TC, what us the best way to create scripts, shared libraries and data tables? Is it done in a Project Suite with all scripts/functions?
Thanks in advance
Re: Project/Script best practices
Actually, this depends on your needs. There's no 'best' way to organize your tests, and there's no single solution for all cases. TC provides ways to create a custom test structure (test items, units, projects, etc.), but it's up to you to decide what structure will be the most convenient in your case.