Workspaces

Goal

Understand Copiqo's 4-tier data model to keep your test credentials organized across multiple projects and testing environments without clutter.

Data Hierarchy Model

Data inside Copiqo is organized hierarchically as follows:

Workspace
└── Group
    └── Record
        └── Field

1. Workspace The top-level container representing a project, client, or specific cluster of environments. Each workspace is configured with its own Domain Rules for auto-activation.

2. Group Used to organize records inside a workspace by usage scenario or user role. - *Examples:* Customer Logins, Vendor Logins, Test Credit Cards, Mock Addresses.

3. Record A complete dataset representing a single test case or test entity. It bundles multiple related fields together. - *Examples:* VIP Buyer Account, Blocked Merchant, Visa Successful Card.

4. Field The smallest unit, containing a key (field name) and a value. Field names are used by Copiqo's autofill engine to match the name or id attributes of HTML inputs on the page. - *Examples:* email = admin@myproject.com, password = 123456.

---

Real-World Workspace Example

Here is a structured representation of a staging checkout workspace:

Workspace: Payment Platform - STAGING
├── Group: Test Accounts
│   ├── Record: Admin Account
│   │   ├── email = admin@checkout.internal
│   │   └── password = secret_admin_pass
│   └── Record: Basic Buyer
│       ├── email = buyer@checkout.internal
│       └── password = basic_buyer_pass
└── Group: Mock Credit Cards
    ├── Record: Visa Passed Card
    │   ├── card_number = 4242 4242 4242 4242
    │   ├── card_holder = STAGING USER
    │   └── cvv = 123
    └── Record: Master Declined Card
        ├── card_number = 5555 4444 3333 2222
        ├── cvv = 999

---

Best Practices