Projects/Script Organization best practices
Hi, I wonder if there is any best practice for the organization of projectsuites/projects/script that take into account versionning of tested solution. We have several solutions with ...
Forum Discussion
Thank You David for your response,
My problem is that we have a product P which is made up of 4 specific solutions S1,S2, S3,S4 which in turn share severel things (binaries, install procedures).
So, i naturally created 1 ProjectSuite for the global product P, define variables shared by all solution Sn
I have created sub-directories S1, S2 ... to simulate the solution under which i create a project for each functionnalities i have to test.
I have created a project Install and a project Common, under ProjectSuite P, that can be shared between all the projects
by referencing the scripts (Since they are in the same ProjectSuite).
If i want to test a specific solution, i check from the project suite , the project Install and all the project under directory S1
=>I would have like to be able to create a group of test item on the ProjectSuite in order to group all the functionalities of a solution (install and all projects under the directory Sn) so that I would be able to test each solution without to check/uncheck project from the ProjectSuite
Now, if i create a ProjectSuite per Solution, how do i share information between ProjectSuite ??
-> i have to duplicate variables , clone projects (by example project Install, and Common) since we can't share/reference script from one ProjectSuite to another. -> for me , it's a bad thing
If i had to make a correction, i will have to report the changes in all the copies (so at least 3 copies)..... -> Bad things ...
If i create a ProjectSuite Install, i have to externalize the logic out from testComplete to run the Install test and the Acceptance test of the solution.
The last solution is to create 1 project per solution, and have a script for each functionnality tested. In that case, i will have many
files, regiosn , tables under Stores and it will quickly be unmanageable.
It seems to me that If i would be able to insert a ProjectSuite under another ProjectSuite , it will solve a large part of the problem.
Regards,
karim SOUAK
My problem is that we have a product P which is made up of 4 specific solutions S1,S2, S3,S4 which in turn share severel things (binaries, install procedures).
So, i naturally created 1 ProjectSuite for the global product P, define variables shared by all solution Sn
I have created sub-directories S1, S2 ... to simulate the solution under which i create a project for each functionnalities i have to test.
I have created a project Install and a project Common, under ProjectSuite P, that can be shared between all the projects
by referencing the scripts (Since they are in the same ProjectSuite).
If i want to test a specific solution, i check from the project suite , the project Install and all the project under directory S1
=>I would have like to be able to create a group of test item on the ProjectSuite in order to group all the functionalities of a solution (install and all projects under the directory Sn) so that I would be able to test each solution without to check/uncheck project from the ProjectSuite
Now, if i create a ProjectSuite per Solution, how do i share information between ProjectSuite ??
-> i have to duplicate variables , clone projects (by example project Install, and Common) since we can't share/reference script from one ProjectSuite to another. -> for me , it's a bad thing
If i had to make a correction, i will have to report the changes in all the copies (so at least 3 copies)..... -> Bad things ...
If i create a ProjectSuite Install, i have to externalize the logic out from testComplete to run the Install test and the Acceptance test of the solution.
The last solution is to create 1 project per solution, and have a script for each functionnality tested. In that case, i will have many
files, regiosn , tables under Stores and it will quickly be unmanageable.
It seems to me that If i would be able to insert a ProjectSuite under another ProjectSuite , it will solve a large part of the problem.
Regards,
karim SOUAK
