Project Structure

The Drizz Desktop App organizes all test assets within a structured project workspace. The File Explorer provides a unified view of all tests, modules, and folders, enabling teams to maintain clean, scalable automation repositories. This section explains how project items are organized and how users interact with them during authoring and execution.

Project Structure Overview

Drizz Desktop groups automation assets into two primary categories:

1. Tests — individual automation flows authored screen-by-screen

2. Modules — reusable blocks of logic that can be inserted into any test

Both are accessible and manageable through the File Explorer, which acts as the central navigation and organization interface for all project assets.

File Explorer

The File Explorer provides a clear, hierarchical view of all files within the selected project. Key capabilities include:

1. Folder-Based Organization

1. Create folders to group tests by feature, module type, sprint, or team.

2. Expand or collapse folders for cleaner navigation.

3. Maintain large automation suites without clutter.

2. Test Files

A test represents a full end-to-end flow or a functional scenario. Test files:

1. Contain sequential command steps defining the flow

2. Are fully editable through the Test Editor

3. Can be run locally or through cloud Test Plans

4. Support validations, conditions, scrolling, system commands and reusable modules

5. Are saved with a readable name for easier identification (Example: “T01 – Invalid Search Feedback Flow”)

3. Modules

Modules allow repeated test logic to be authored once and reused across multiple tests. Common use cases:

1. Login flows

2. Location setup

3. Precondition setup

4. Cleanup flows

5. Shared UI interactions

Modules appear in the File Explorer with a green “M” badge, making them easily distinguishable from test files.

Modules:

1. Can be inserted into any test using the editor

2. Improve maintainability by centralizing frequently reused steps

3. Reduce duplication and ensure consistency across large suites

4. Online vs Local Workspace

At the top of the File Explorer:

1. Online view syncs with the cloud project

2. Local view displays drafts or locally stored files

3. Switching between environments helps teams manage work before publishing

5. New File Creation

The New File button allows users to quickly create:

1. A new Test

2. A new Module

3. A new Folder

All files immediately appear in the structured hierarchy.