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

SunRav TestOfficePro: Complete Setup & First-Time Checklist

1. System requirements (minimum)

• 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

2. Pre-install preparation

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

3. Installation steps

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

4. Initial configuration

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

5. Project onboarding checklist (first project)

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

6. Post-install verification tests

• License activation check: Confirm license expiry and concurrent-seat count.
• User login: Test logins for admin and non-admin users.
• Project creation and deletion: Verify lifecycle actions.
• External integrations: Trigger a test issue creation in Jira and send a