Test script for testing a new release of Amiberry

Release Test Script

Before start testing make sure that all automated builds are green. Prerequisites: A machine to test on, kickstarts (1.2 until 3.2.2) for A500, A1200, A3000, A4000 and A4000T. Workbench 3.1,3.1.4 or 3.2. Some Amiga and amiberry knowledge.

Ensure Amiberry builds from a clean environment using method described in README.MD.

Do the following in both KMS, Wayland and Xorg. None of steps should fail.

1. Start Amiberry. Configuration GUI should appear.
2. Press Restart. Amiberry should restart.
3. Configure path to kickstarts, and use quickstart to configure a A500. Start emulation and wait a few seconds before the kickstart screen appears. Go back to GUI and resume emulation again. Go to back to GUI yet again and turn on Status Line native. Go back to emulation and ensure you get at least 50 fps.
4. Exit Amiberry, and start it again (not restart) and load configuration. Ensure that correct machine / configuration was loaded.
5. Do 3-4 with A1200, A3000, A4000 and A4000T. Ensure that correct rom is selected on the rom page.

Use Quickstart to configure a machine, and save the configuration with a unique name. Delete it. Use Quickstart to configure a machine, save it with the default name (default) - delete it Use Quickstart to configure a machine, save the configuration with a unique name. Change the Description, and save.

Boot with a ADF (game, or workbench disk doesn't matter) Change floppy drive speed and repeat the above.

Check that Z2 and Z3 memory works by first booting with only Z2 memory, then with Z2 and Z3, and then with only Z3.

Boot the AmigaOS 3.2 iso. Hold both mouse buttons when you start emulation and choose CD0 as boot device.

Install Workbench to a directory (Hard drives/CD, Add directory) and make sure it boots and works.

Create a HDF file (truncate -s 1G System.hdf Add it with UAE as controller, make sure you can format it when you start from the Install ADF (RDB emulation) Install workbench to it, make sure if boots and works properly.

Create a HDF file truncate -s 1G System.hdf Add it with A600/A1200/A4000 IDE as controller, make sure you can partition it and format it when you start from the Install workbench disk. Install workbench to it, make sure if boots and works properly.

Boot to workbench and use the three finger salute in order to reboot the emulated Amiga. Ensure that the keyboard works after workbench is loaded again.

Add a UAE Zorro III card and install P96. Make sure RTG is working.

Vulkan Rendering (Phase 03 - Experimental)

When testing a build with Vulkan renderer enabled (-DUSE_VULKAN=ON -DUSE_OPENGL=OFF), perform these additional smoke checks:

Build Verification

1. Confirm the build completes without errors (Vulkan requires MoltenVK/Vulkan SDK headers).
2. Verify the binary contains Vulkan-specific log strings using strings Amiberry | grep -i "VulkanRenderer".

Startup and Initialization

1. Start Amiberry with --log flag to capture initialization messages.
2. Check for these deterministic Vulkan initialization logs:
   • VulkanRenderer: initialization complete (swapchain NxM, N images)
   • VulkanRenderer: found suitable GPU: or VulkanRenderer: selected GPU:
   • VulkanRenderer: VMA allocator created
   • VulkanRenderer: logical device created
3. Confirm no Vulkan validation-layer errors in the log.

First Frame and Present

1. Start emulation (any quickstart model is sufficient for a few seconds).
2. Check for these deterministic first-frame logs (may appear during or after first frame submission):
   • VulkanRenderer: first upload complete
   • VulkanRenderer: first submit complete
   • VulkanRenderer: first present complete

Resize and Swapchain Recreation

1. While emulation is running, resize the window.
2. Check for these deterministic resize/recreate logs:
   • VulkanRenderer: swapchain recreated (NxM, N images) (if swapchain was recreated)
   • VulkanRenderer: resize skipped due to zero extent (0x0) (if window was minimized)
3. Confirm emulation continues smoothly after resize.

Fallback Renderer Regression Check

1. Rebuild with USE_VULKAN=OFF and USE_OPENGL=ON (the default).
2. Verify the build completes and the binary contains OpenGL-specific strings but NOT VulkanRenderer: strings.
3. Confirm the standard OpenGL renderer works in the same test scenarios.

Evidence Isolation

• Vulkan-specific log strings (VulkanRenderer:) should only appear in Vulkan builds.
• OpenGL-specific strings should only appear in OpenGL builds.
• Use strings on the binary to verify isolation: strings Amiberry | grep -i "VulkanRenderer" vs strings Amiberry | grep -i "OpenGL".