Updated: 4/21/2025

  • Home
  • About
    • Welcome
    • Training / Consulting
    • History
    • Attribution
    • Contribute Case Studies
  • The gDS Facility
    • Disassembling DBMSs
    • gDS Overview
    • Working With gDS Tables
    • .dd File Format
    • gDS Generated Code
    • Managing Concurrency
  • AI R&D
    • Introduction
    • Initial Work (Post 1)
  • Building Test Platforms
    • Development Phases
    • Interface To The SUT
    • Test Runs and Cycles
    • Screen Displays
    • Static/Dynamic Config.
    • Managing Concurrency
    • Additional Functionality
  • Case Studies & Code
    • Overview & TOC
    • Case Study 1
    • Case Study 2
    • Case Study 3
    • Case Study 4
    • Case Study 5
    • Case Study 6
  • Webinars
    • Webinar Notes
  • More
    • Home
    • About
      • Welcome
      • Training / Consulting
      • History
      • Attribution
      • Contribute Case Studies
    • The gDS Facility
      • Disassembling DBMSs
      • gDS Overview
      • Working With gDS Tables
      • .dd File Format
      • gDS Generated Code
      • Managing Concurrency
    • AI R&D
      • Introduction
      • Initial Work (Post 1)
    • Building Test Platforms
      • Development Phases
      • Interface To The SUT
      • Test Runs and Cycles
      • Screen Displays
      • Static/Dynamic Config.
      • Managing Concurrency
      • Additional Functionality
    • Case Studies & Code
      • Overview & TOC
      • Case Study 1
      • Case Study 2
      • Case Study 3
      • Case Study 4
      • Case Study 5
      • Case Study 6
    • Webinars
      • Webinar Notes
  • Sign In
  • Create Account

  • Bookings
  • My Account
  • Signed in as:

  • filler@godaddy.com


  • Bookings
  • My Account
  • Sign out


Signed in as:

filler@godaddy.com

  • Home
  • About
    • Welcome
    • Training / Consulting
    • History
    • Attribution
    • Contribute Case Studies
  • The gDS Facility
    • Disassembling DBMSs
    • gDS Overview
    • Working With gDS Tables
    • .dd File Format
    • gDS Generated Code
    • Managing Concurrency
  • AI R&D
    • Introduction
    • Initial Work (Post 1)
  • Building Test Platforms
    • Development Phases
    • Interface To The SUT
    • Test Runs and Cycles
    • Screen Displays
    • Static/Dynamic Config.
    • Managing Concurrency
    • Additional Functionality
  • Case Studies & Code
    • Overview & TOC
    • Case Study 1
    • Case Study 2
    • Case Study 3
    • Case Study 4
    • Case Study 5
    • Case Study 6
  • Webinars
    • Webinar Notes

Account


  • Bookings
  • My Account
  • Sign out


  • Sign In
  • Bookings
  • My Account

.dd File Format

This section describes the makeup of a ".dd" file. For some examples of some .dd files, browse to the URL below and examine the “case study” folders:


        https://github.com/talborough/testingComplexSystems


Note that all the data (lists and dictionaries) created by the declarations described below is “globally shared.”


Note also that all variable names must follow Python's naming rules except – underscores are treated as separators in the various gDS table, column, and index names.

defineTable

defineTable <table name> — This starts the definition of a table. <table name> is mandatory and can be anything. There can be no underscores in the table name. 

defineColumn

defineColumn <column name> [<default value>] — This keyword defines a column in a table. <column name> is mandatory> <default value> is optional. The types of column names are:


<this table name>_<that table name>_Ref — This defines a reference from the current row in <this table name> to a row in <that table name>.


<this table name>_<anything but the above> — This defines an ordinary column in the current table.


A “Name” column must exist in every table. It is used to identify the terminal row of a reference when dumping a referring table. It does not have to hold unique values unless the column is also cited in a defineIndex citation.


A “RowStatus” column must exist in every table. It will be appended last to the table in all cases. See the Test Platform tab for more information about the uses of this column.

defineIndex

defineIndex <index name> — This keyword defines an index for one column of the table. <index name> is mandatory and must follow the format <table name>_<column name>2Ref, where the column name must be a column in the current table.


Code is generated to check for duplicate values on inserts in the "AddARow" routine, and if detected, the program halts, displaying an execution stack trace.

endTable

 This ends the current table definition.

defineUnary

defineUnary <unary name> <initial value> — This keyword defines a list of size (1) to use as a solo value (the Python "multiprocessing" feature only supports "lists" and "dicts").  

defineList / defineDict

defineList / defineDict <variable name> — These keywords generate an empty list or dict. 

Copyleft © 2025 Testing Complex Systems - All Rights Reserved.

Powered by

This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

DeclineAccept