Skip to content

TESTING_GUIDE.md

Latest commit

 

History

History
60 lines (48 loc) · 1.58 KB

TESTING_GUIDE.md

File metadata and controls

60 lines (48 loc) · 1.58 KB

Testing RPM_sync.py with Tart VMs

Step 1: Start the VMs with GUI

tart run fedora-vm1 &
tart run fedora-vm2 &

Step 2: Configure VMs through GUI

For each VM:

  1. Complete the initial setup (create user account)
  2. Enable SSH access
  3. Note the username you created (default is usually 'admin' or 'fedora')

Step 3: Update the scripts with your username

Edit both setup_vms_for_test.sh and run_sync_test.sh:

  • Change VM_USER="admin" to match your actual username

Step 4: Setup VMs for testing

./setup_vms_for_test.sh

This will:

  • Install unison and required packages
  • Copy RPM_sync.py to both VMs
  • Verify system type (dnf vs rpm-ostree)

Step 5: Run the sync test

./run_sync_test.sh

This will:

  • Install different packages on each VM (git on VM1, wget/curl on VM2)
  • Test syncing from VM1 to VM2
  • Test syncing from VM2 to VM1
  • Show package status before/after each sync

Expected Results

  • Both VMs should end up with the same set of packages
  • The sync should work bidirectionally
  • You should see Unison synchronizing the package lists

Manual Testing

You can also test manually by SSH'ing into the VMs:

# SSH into VM1 (replace with your actual VM IP and username)
ssh [VM_USER]@[VM1_IP]

# Run the sync script (replace with your VM2 IP)
python3 RPM_sync.py -r [VM2_IP]

Troubleshooting

  • If SSH doesn't work, ensure you've enabled SSH in the VM's GUI
  • If Unison fails, check that both VMs have unison installed
  • If package installation fails, check sudo permissions
  • VM IPs might be different - check with tart ip fedora-vm1