Forum Discussion
Thank you for the updates
I am seeing some drawbacks with Add Existing Item Feature in TestComplete
There are some function/libraries that I have created which are reusable . When we create new project then we add those functions/libraries using Add Existing Item. When push this project in Source version Control . After this when we execute the tests build through Jenkins then we get the error the function is located to some other files/directories . Due to this I have to copy those functions/libraries to the the same folder where project is located.
My concern is if TestComplete provide the ability to add those function in the newly created project using the feature "Add Existing Item" which is easy but then it will create such issue after checking in the TestComplete tests to Source version control and execute through Jenkins or other build management software.
Thanks
Nishchal.
- tristaanogre7 years agoEsteemed Contributor
The answer is to make sure that, when you have your Jenkins job to pull down your code, you pull down the "shared" code as well. What we do for those shared/reusable libraries is we put them in a "common" folder and not in a project specific folder level. We then make sure that, in our "pull" from our source control, we include the project AND the "common" folders. This is the better solution and will solve the problem you've described.
Related Content
- 11 months agoIrinaManea
- 12 months agoMarcusBengtsson
- 10 months agoAnabelle
- 13 years agomrouse
Recent Discussions
- 9 hours agosimonaferrara
- 18 hours agoSubhraDas