Testing

Beta Tester Guide

Use this guide to test VMNexor features and report useful feedback during beta evaluation.

VMNexor documentation is actively evolving. Some features, wording, and screenshots may change during beta.

Beta purpose

The VMNexor beta is designed to validate real hosting workflows before wider release. The goal is to find edge cases in provisioning, templates, billing actions, customer controls, and operational recovery.

What to test first

  • Login and account access
  • Customer portal loading
  • Documentation clarity
  • Basic VM lifecycle controls
  • Console access
  • Support contact flow

Provisioning tests

  • Create a Linux VM
  • Create a Windows VM if available
  • Confirm IP assignment
  • Confirm DNS works inside the VM
  • Confirm the VM appears correctly in VMNexor
  • Confirm the VM appears correctly in Proxmox

Lifecycle tests

  • Start VM
  • Stop VM
  • Restart VM
  • Suspend from billing/admin flow
  • Unsuspend from billing/admin flow
  • Terminate only on a disposable service

Reinstall tests

  • Reinstall using the same OS family
  • Reinstall using a different allowed template
  • Confirm warning text is clear
  • Confirm old data is removed as expected
  • Confirm new login/password behaviour works
  • Confirm blocked templates cannot be selected

Windows-specific tests

  • Confirm Windows boots after provisioning
  • Confirm QEMU Guest Agent is running
  • Confirm password or first-login behaviour works
  • Confirm console access works
  • Confirm reinstall behaviour matches the selected template

Linux-specific tests

  • Confirm SSH access works if provided
  • Confirm DNS resolution works
  • Confirm routed or bridged networking behaves correctly
  • Confirm reboot does not break networking
  • Confirm reinstall applies networking again

Good bug reports include

  • What you were trying to do
  • Account email or tester name
  • Service name or ID
  • Selected template
  • Node name if visible or provided by support
  • Approximate time of issue
  • Exact error text or screenshot
  • Whether retrying changed the result

Feedback that helps most

  • Confusing wording
  • Missing warnings before destructive actions
  • Pages that feel unfinished
  • Actions that take too long without feedback
  • Anything that feels risky for a real customer
  • Anything that made you unsure what happened

Beta expectations

VMNexor is actively evolving. Features, wording, screenshots, and flows may change during beta. Testers should avoid using beta services for critical production workloads unless explicitly agreed with the operator.