Forum Discussion
I think you will find that breaking your tests up into modules somehow, whatever works for you, is better in the long run than trying to make one huge test that works for everything all the time. Projects and Project Suites are helpful for that.
https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/creating.html
I do understand the idea behind Projects in a suite. We are already leveraging this by creating separate projects for our different country sites, allowing us to share workflows where they are similar, but specify specific differences for each site.
I do not understand how splitting off these header and footer tests into a separate project would be beneficial though. It has the same problems as my solution #1 above as it creates additional copies of the elements anyway, but then also adds additional work in maintenance by worrying about an additional project, and then additional problems outside of the test suite with our pipeline. I don't see what we actually gain from this solution that we do not using my proposed workaround #1, and I do see more tradeoffs in implementing it.