Workspace

Ember organizes work as project → task → artifacts, not disposable chat threads.

Core concepts

Project

A project maps to a product or release line. Store:

• PRDs, API specs, test standards
• Environment notes and defect summaries
• Approved cases, regression lists, and reports

This project context is reused by later tasks automatically.

Task

A task is one testing activity, e.g.:

• Regression scope for a release
• API cases and assertion lists
• E2E happy-path steps
• Defect retrospectives

Iterate in the same task—history stays linked to the goal.

Agent Apps

Test workspace Apps batch runs and automation flows into reusable entry points.

Typical flow

1. Create or select a project
2. Add context to project materials
3. New task → pick model and experts / Skills
4. Draft → refine → save back to project context
5. Next task reuses saved materials

Mobile testing

The mobile testing workspace can tie into tasks—device runs, screenshots, and logs feed back into context.

Tips

• One task per release candidate for traceability
• Load context before generation
• Consistent naming (module / priority / env)
• Promote stable flows to Skills—see Experts & Skills