Migrating to SunRav TestOfficePro: Step-by-Step Guide for IT Teams

SunRav TestOfficePro: Complete Setup & First-Time Checklist

OS: Windows 10 (64-bit) or later / macOS 11.0 or later
CPU: Dual-core 2.5 GHz or faster
RAM: 8 GB (16 GB recommended)
Disk: 5 GB free for application + 10 GB for projects/logs
Network: Stable broadband (for license activation, updates, cloud sync)
Permissions: Administrator rights for install; firewall allowed for program and updater

Backup existing projects: Export or copy any current project files that might conflict.
Check license & credentials: Ensure you have the license key, admin user account, and any SSO/OAuth info.
Disable conflicting software temporarily: Antivirus or aggressive endpoint tools can block installer actions—plan to whitelist if needed.
Confirm network access: Port 443 and the domain(s) listed in your vendor docs should be reachable.
Gather runtime dependencies: If your deployment uses database or messaging (e.g., PostgreSQL, Redis), ensure version compatibility.

Download installer: Get the latest installer from the official distribution point.
Verify checksum: Confirm the file integrity (SHA256) to avoid corrupted installs.
Run installer as admin: Follow prompts; choose “Typical” for single-machine and “Custom” for server/enterprise options.
Select installation directory: Prefer a stable path (avoid user temp folders).
Install prerequisites: If prompted, allow .NET runtime (Windows) or necessary runtimes on macOS.
Complete installation and restart (if required).

Launch TestOfficePro: Sign in with the admin account and activate your license.
Set global preferences: Timezone, default project folder, autosave interval, and update settings.
Configure user roles: Create admin(s), project managers, and testers with appropriate permissions.
Integrate with directory/SSO: Connect to LDAP/Active Directory or SSO provider if required.
Connect external services: Link issue trackers (Jira), CI systems, and notification channels (email, Slack).
Set up backups: Schedule automated backups of config and project data.

Create project: Define name, key, type (functional / performance), and retention policy.
Import test assets: Upload or import existing test suites, scripts, or templates.
Configure environments: Add test environments (staging, QA), with target endpoints and credentials stored securely.
Define test schedules: Set daily/weekly runs and assign owners.
Set alerts & thresholds: Define pass/fail conditions, performance thresholds, and notification rules.
Run a smoke test: Execute a small suite to validate connectivity, permissions, and basic functionality.