Screen Capture Harness

This module is not a business feature; it is a throwaway harness used to produce documentation images. It runs browser-driven tests against the transport module on an anonymised copy of a database and saves each screen as a picture, in light and dark themes. It depends on the transport module, Fleet and Accounting. It is meant for developers and documentation writers and is not installed for daily users.

1. 1

   Prepare the anonymised database

   The team restores an anonymised clone of the demo database and installs the transport module and this harness. Real names and brands are not present in the pictures. The harness is tagged so it never runs with the standard test suite.

   • Install transport plus the harness
   • Anonymised clone only
   • Runs only with its own test tag
2. 2

   Run the capture test

   A developer runs the module tests with the screenshots option. The test opens each planned screen in the built-in browser, waits for it to load and takes a picture. Screens are grouped in the plan: dashboard and settings, master data, pricing, operations, corrections, treasury and transfers, settlement, and statements and reports.

   • Test tagged for this harness
   • Plan grouped by business area
   • Pictures saved with stable names
3. 3

   Prepare records for printable reports

   Some reports need a wizard record or a demo document to exist first. The test creates the missing draft records and context-carrying wizard actions, then renders each report as HTML. A caption is stored for each picture.

   • Creates draft demo records
   • Wizard actions with context
   • Caption per picture
4. 4

   Capture tall screens and tabs

   Additional tests take taller pictures of long forms and one picture per form tab. The guided tour is marked as seen first so it does not cover the screen. Each picture is taken in both light and dark themes.

   • Tall form captures
   • One picture per tab
   • Light and dark themes
5. 5

   Collect and use the pictures

   The pictures are written to the screenshots folder of the database run. Writers copy them into the user guide. The module can be uninstalled afterwards because it holds no data of its own.

   • Output in the screenshots folder
   • Used for the user guide
   • No data of its own

Back to version applications