"Common" or "Lib" Project
Test Project Library
If I have a parameterized test that is used by several other Test Projects in my TestComplete suite, should I put that test with others in its own TestComple Project that doesn't gets run directly along with other similar tests and have a "library" project of common keyword tests?
For example, I have test, "Load_spkpro[spkpro_name]" where spkpro_name is the name of an app-specific project. I have test projects Test_IM_spkpro, Test_Q_VLD_spkpro, Test_Z_TT_spkpro, Test_C_SA_spkpro and so on. Each spkpro project in the application has different functionality, different graphs, different tables, different operations, and so really different tests. But before the project is loaded and even when the project is loaded and verified, there are common steps and checkpoints that work for all spkpro project types. Should Load_spkpro be in a separate project with other common tests and treated like a library that doesn't get run directly?
What's the approach in TestComplete for having a library of tests that get executed from multiple projects?
Let me know if any of the above is not clear and I'll elaborate some more.