Updated: 8/14/2025

  • Home
  • About
    • Welcome
    • Training / Consulting
    • History
    • Attribution
  • The gDS Facility
    • Disassembling DBMSs
    • gDS Overview
    • Working With gDS Tables
    • .dd File Format
    • gDS Generated Code
    • Managing Concurrency
  • AI R&D
    • Introduction
  • 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
  • Webinars
    • Webinar Notes
  • More
    • Home
    • About
      • Welcome
      • Training / Consulting
      • History
      • Attribution
    • The gDS Facility
      • Disassembling DBMSs
      • gDS Overview
      • Working With gDS Tables
      • .dd File Format
      • gDS Generated Code
      • Managing Concurrency
    • AI R&D
      • Introduction
    • 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
    • Webinars
      • Webinar Notes

  • Home
  • About
    • Welcome
    • Training / Consulting
    • History
    • Attribution
  • The gDS Facility
    • Disassembling DBMSs
    • gDS Overview
    • Working With gDS Tables
    • .dd File Format
    • gDS Generated Code
    • Managing Concurrency
  • AI R&D
    • Introduction
  • 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
  • Webinars
    • Webinar Notes

Screen Displays

I have always used text-oriented screen displays because of their simplicity. You can also use a graphical UI package.


One behavior of text-oriented displays is that the screen can “flash” when displaying. To prevent that, the text is appended to a single variable as it is built, and it is then displayed on the screen with a single “print” statement.


You will have to evaluate whether to lock the building of the display. On one hand, it might be acceptable to have a 3-second irregularity caused by accessing a table without a lock. On the other hand it would be unacceptable for the test platform to fail while displaying a table being compressed.

Testing Complex Systems

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