Skip to main content

​
Quick Navigation

Installation

Deploy TestAuto2 solution into your Polarion project.

User Management

Configure roles, permissions, and team access.

Configuration

Customize project settings and RTM model properties.

Updates

Upgrade to new TestAuto2 versions safely.

Backup & Recovery

Protect project data with backups and restore procedures.

​
Administration Tasks

Install TestAuto2 Solution — Deploy the TestAuto2 solution package into a new Polarion project, including RTM model, risksheet/powersheet configurations, custom fields, and velocity macros. Manage User Permissions — Assign roles (Safety Engineer, Design Engineer, V&V Engineer, Config Manager, Program Manager) and configure work item type permissions for your team. Configure Project Properties — Set project name, prefix, lead, timeline, and customize RTM domain model settings to match your organizational structure. Update Solution Version — Upgrade TestAuto2 to a new version, migrate configurations, and validate backward compatibility. Backup and Restore Project — Create project backups, export/import project data, and recover from incidents.

​
Key Administration Areas

diagram

​
Common Administration Workflows

​
First-Time Setup

  1. Install Solution — Deploy TestAuto2 package into Polarion
  2. Configure Project Properties — Set project name, lead, RTM model
  3. Manage Permissions — Assign roles to team members
  4. Validate Configuration — Run consistency check to verify RTM model and risksheet configs

​
Ongoing Maintenance

  • Monitor project health via dashboard metrics
  • Back up project data regularly (weekly recommended)
  • Review user access levels quarterly
  • Update solution when new versions are available

​
Scaling to Multiple Teams

  • Create subsystem-level risksheets for design teams
  • Configure component RTM sheets for traceability per design team
  • Set up role-based dashboards for different engineering disciplines
  • Establish document approval workflows by team
Document all custom configuration changes in your project’s Configuration Management space. Include who made the change, when, and why—this creates an audit trail for ISO 26262 compliance.
Always test solution updates in a non-production environment first. Some versions may require RTM model migration or custom field adjustments.