Thanks for the articale links:
Per Team City Jobs I use, and a way to I haveTestComplete know what env. I want my scripts to run against.
i.e. QA, STAGING, PROD
I use the Tag parameter property in the Task and NetworkSuite objects as that control.
I was trying to see if there was another way to use the Tagging of Scripts to break the test suite run into the areas of functionality by how the tagging is done per test script.
I will go ahead and tag the scripts for having those set for future use.
What I may do now here is further tweak the way I am using this Tag properity and include additional info along with it.
i.e. QA_MainMenu, STAGING_ViewEdit, QA_Printing, QA_LoginLogout
Then on my OnStartTest event, I can parse and set my Global vars so when the Jobs\Tasks script is hit it would now know the test environment and the area of functionality to test. I would then just need to add more into the Tasks scripts, used by my Slaves, to now recognize not just the test env but now also the area of functionality to test against or default back to running the complete package of scripts originally set for the Slaves.
All of everyone's comments is clearing up my approach here for what I need to do.
This is all prep work to be able to run continuous testing on specific functional areas of a app per Dev changes checked in and avoiding wasting script runtine on areas not affected by Dev changes.
DevOps Cont. testing per Dev checkin\build\deploy\test.
Thanks All
