Projects/Script Organization best practices

Hi,



Why couldn't we add a ProjectSuite into another ProjectSuite or Project ???

Why couldn't we create group of test Item on a ProjectSuite ?



I have a global Product P which has 4 specifics Sub-Solution Pa, Pb Pc, Pd

Pa, Pb, Pc and Pd share many features ( same binaries, same install procedure (which contains 4 steps (exe setup) ...)

To simulate Pa, Pb ... I use a directory DirPa, DirPb ..

and add under each  directory,  projects to test functionnalities f1, f2 (Paf1, Paf2 ...)



P

|-Dir Pa

|     |- Paf1, Paf2...

|-Dir Pb

|     |- Pbf1, Pbf2...

...

|-Install

|     |- PInst1, PInst2, Pinst3, Pinst4

|-Common

|     |- PCom1, PCom2...



But now, if i want to test all the functionalities of product A, i cannot create "test item" on the folder DirPa

which simulate a projectSuite.



I would like to create group of test item on the highest level P in order to group all the item of the sub-group Pa.

But we cannot create Group on a projectSuite....



So how can we do:

  Create one ProjectSuite, with 4 Projects (Pa, Pb, Pc, Pd) and create all the functionnal scripts under each project  ???

   back to my question on versionning, if i want to test  the version V2 of product A and support tes regression of the V1.2 and V1.0 

   I have to create project Pa_V1.0 with all scripts, Pa_V1.1 with all scripts(modified, new ones and deleted ones) an Pa_V2.0 with all scripts(modified, new ones and deleted ones)



So what do AutomatedQA  consider a good approach ?

How do we have to manage our projectsuite/project to support multiple products sharing elements and supporting versionning ?



Regards.

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























 



 

Hi Karim,





It seems that you need something like project suite configurations. I have registered your request in our database, thank you.





The best solution I can suggest is using several project suites. Please note that you share the same project among several suites. So, you can add your Install and Common projects to all your project suites.





However, this does not solve the problem with project suite variables. To workaround this restriction, you can store the needed values in a separate storage file (e.g. a CSV or Excel file) and load information from this file to project suite variables at the beginning of your tests. For example, you can set the Common project to be the first project in all your project suites and the only test item in this project will read the needed data from external storage.





Please let me know if you need help in working with CSV or Excel files.