Problem:
Our team has several Project Suites across all of our tested applications, and we are always looking to add more. To that end, we've created many scripts in a kind of framework to streamline our process. When we start working on a new Project, we have to manually import all scripts/event handlers/other Project items that we use in a more or less universal fashion.
This idea addresses two pain points in our current new Project creation process. The first is that this process takes a fair amount of time, from importing the scripts to adding the necessary project items and wiring up the necessary event handlers and other project errata. The other is that this is a manual process with many potential points of failure, and we want this to be as repeatable as possible so we can hand the process off to non-programmer QA.
Proposed Solution:
Add an ability to create Projects/Project Suites based on templates. A possible solution that would not involve permanently adding files to the TestComplete app or AppData folder could be adding an option to use an existing Project/Project Suite as a template.
An example workflow:
- User selects the file option File>New>New Project Suite...
- User is presented with the option to create the Project Suite from scratch or Create from a Template
- User selects the Create from a Template option
- User navigates to and designates a Project Suite to use as a template
- User selects a name for the new Project Suite
- User selects a location for the new Project Suite
- TestComplete creates a new Project Suite with all files and settings from the Template Project with the new name that was designated by the user.
