What is the “best” way to store scripts?

Question

I have hundreds of scripts for testing a component. Each of these scenarios contains a set of indexes and individual records.

Subscribers can be used in several TC_Level scripts and even in other indexes.
Each script has a unique name.

Example:

TC_1
  |  
 (1) Subscript_a  
  |  |  
  | (1) Record  i
  |  |  
  | (2) Record  ii
  |  
 (2) Subscript_b  
  |  |  
  | (1) Subscript_c
  |  |  |
  |  | (1) Record_i  
  |  |  |  
  |  | (2) Record_iii  
  |  |
  | (2) Record_ii  
  |  
 (3) Record_iv  
  |  
 (4) Record_v  
  |  
  ...  

I would like to

• save my scripts in a container.
• read them as a tree in my script engine.

What type of container should I use?

Possible containers (but not limited to): directory, database, XML file, spreadsheet, flat file, ...

Please, when making proposals, also include a short sample (not necessarily a code) of the storage structure.

treeviews #, , parentID ( ), .

Answer 1

+ .

:

• .
• - - .

Answer 2

, .

, , . dat , , , . tar, .

 Shared
 |    |
 |    Subscript_a  
 |    |
 |    Subscript_b
 |    |  
 |    Subscript_c  
 Test_Case_1
 |         |
 |         SUBSCRIPT_B_DIRECTORY
 |                             |
 |                             link to ../../Shared/Subscript_b
 |                             |
 |                             SUBSCRIPT_C_DIRECTORY
 |                                                 |
 |                                                 link to ../../../../Shared/scri_c
 Test_Case_2
 |         |
 |         SUBSCRIPT_C_DIRECTORY
 |                             |
 |                             link to ../../Shared/Subscript_c
 Test_Case_3
           |
           SUBSCRIPT_A_DIRECTORY
           |                   |
           |                   link to ../../Shared/Subscript_a
           SUBSCRIPT_B_DIRECTORY
                               |
                               link to ../../Shared/Subscript_b

. , , Test_Cases. , $SHAREDTOP . , . , tar UNIX.

Answer 3

. , "tar" ( - /zip).