Projects & Organization

Projects are the foundation of your testing workflow in Rock Smith. Learn how to create, organize, and manage projects effectively.

What Are Projects

Projects are top-level containers that group related testing assets together:

• Test Flows: The automated test scripts you create and execute
• Discovery Sessions: AI-powered explorations of your application
• Visual Contexts: UI snapshots captured during discovery

Each project is isolated—your projects are private to your account, and all assets within a project share context and settings.

Why use projects?

Benefit	How Projects Help
Organization	Keep related tests together
Context Sharing	Visual contexts from discovery are available to all flows in the project
Clean Separation	Different applications or clients stay isolated
Easy Navigation	Find and manage related assets quickly

Creating a Project

Create a project before starting discovery or building test flows.

1. Navigate to Projects in the sidebar
2. Click Create Project
3. Enter project details:
   • Name (required): A descriptive name for the project (1-200 characters)
   • Description (optional): Additional context about what this project tests
   • Tags (optional): Keywords for organization and filtering
4. Click Create

Your new project starts with zero flows and zero discovery sessions—ready for you to begin testing.

tip

Use descriptive names that identify the application or feature area. "Acme Corp Website" or "Checkout Flow Testing" are clearer than "Project 1".

Project Dashboard

After creating a project, the dashboard shows key metrics and actions:

Project Stats

Metric	Description
Flows	Total test flows in this project
Sessions	Discovery sessions (completed and running)
Visual Contexts	UI states captured during discovery

Quick Actions

• New Discovery: Start exploring your application
• New Flow: Create a test flow manually
• Generate Flows: Create flows from existing visual contexts

Project Context Panel

When you select a project, the context panel appears in the navigation showing:

• Project name and description
• Live stats (flows, sessions, contexts)
• Quick action buttons

This panel persists as you navigate, keeping your project context visible.

Managing Projects

Editing Projects

Update project details anytime:

1. Navigate to Projects
2. Find the project you want to edit
3. Click the Edit button (pencil icon)
4. Update name, description, or tags
5. Click Save

Deleting Projects

Remove projects you no longer need:

1. Navigate to Projects
2. Find the project to delete
3. Click the Delete button (trash icon)
4. Confirm deletion in the dialog

caution

Deleting a project permanently removes all associated flows, discovery sessions, and visual contexts. This action cannot be undone.

Organizing with Tags

Tags help you categorize and filter projects:

Adding Tags

Add tags when creating or editing a project:

• Enter tags as comma-separated values
• Tags can describe client, feature area, testing phase, or any category
• No limit on number of tags

Filtering by Tags

On the Projects page:

1. Use the tag filter dropdown
2. Select one or more tags
3. View only matching projects

Tag Examples

Tag Type	Examples
Client	acme-corp, client-xyz, internal
Feature	authentication, checkout, search
Phase	development, staging, production
Priority	critical, smoke-tests, regression

What Belongs in a Project

Discovery Sessions

Discovery sessions explore your application and capture visual contexts:

• Each session belongs to exactly one project
• Sessions capture screenshots and UI state descriptions
• Multiple sessions can run in the same project
• Visual contexts accumulate across sessions

Test Flows

Test flows define automated test scripts:

• Created manually or generated from discovery
• Each flow belongs to one project
• Flows can reference visual contexts from any session in the project
• Edge case variants stay in the same project as their parent flow

Visual Contexts

Visual contexts are the bridge between discovery and flow generation:

• Captured automatically during discovery
• Shared across all flows in the project
• Used for assertions and element targeting
• Persist even if the discovery session is deleted

note

Keep related flows and discoveries in the same project to share visual contexts. Flows can only use contexts from their own project.

Project Organization Strategies

Choose an organization approach based on your needs:

Single Application Strategy

One project per application

Project: "Acme Website"
├── Discovery: Homepage and navigation
├── Discovery: User authentication
├── Discovery: Product catalog
├── Flow: Login with valid credentials
├── Flow: Search for products
└── Flow: Complete checkout

Best for:

• Small to medium applications
• Teams focused on one product
• Comprehensive end-to-end testing

Advantages:

• All visual contexts available to all flows
• Simple organization
• Easy to track overall coverage

Feature Area Strategy

Separate projects for major features

Project: "Authentication"
├── Flow: Login
├── Flow: Registration
└── Flow: Password reset

Project: "Checkout"
├── Flow: Add to cart
├── Flow: Apply discount
└── Flow: Complete purchase

Project: "User Profile"
├── Flow: Update settings
└── Flow: Change password

Best for:

• Large applications with distinct feature areas
• Teams divided by feature ownership
• Focused testing of specific areas

Advantages:

• Clear separation of concerns
• Easier to assign ownership
• Focused discovery sessions

Environment Strategy

Separate projects for each environment

Project: "App - Staging"
├── Discovery: Staging environment
└── Flows: All test flows for staging

Project: "App - Production"
├── Discovery: Production environment
└── Flows: Smoke tests only

Best for:

• Multi-environment deployment pipelines
• Different test suites per environment
• Tracking environment-specific issues

Advantages:

• Environment-specific visual contexts
• Clear separation of test data
• Easy to compare results across environments

Client Strategy (Agencies)

One project per client

Project: "Client A - E-commerce Site"
├── All discoveries and flows

Project: "Client B - SaaS Dashboard"
├── All discoveries and flows

Project: "Client C - Mobile App"
├── All discoveries and flows

Best for:

• Agencies and consultancies
• Multiple client engagements
• Billing and reporting per client

Advantages:

• Complete client isolation
• Easy to track work per client
• Clean handoff when engagement ends

Best Practices

Naming Conventions

• Use clear, descriptive names
• Include the application or feature name
• Avoid generic names like "Test Project" or "New Project"

Tag Consistently

• Establish a tagging convention for your team
• Use tags for filtering and reporting
• Keep tags concise but meaningful

Regular Cleanup

• Delete projects you no longer use
• Remove failed or incomplete discovery sessions
• Archive or delete outdated flows

Shared Contexts

• Keep related flows in the same project
• Run discovery before creating flows to capture visual contexts
• Use project-level organization to maximize context sharing

Project Scope

• One project per application is a good default
• Split into feature projects only when complexity demands it
• Avoid creating too many small projects—they're harder to manage

Next Steps

• Discovery Sessions - Explore your application automatically
• Working with Flows - Create and run test flows
• Browser Profiles - Set up authenticated testing
• Managing Credits - Understand testing costs