utmapp/UTM

Develop a comprehensive test suite

Open

#2,565 opened on May 23, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Swift (1,707 forks)batch import
enhancementgood first issue

Repository metrics

Stars
 (34,064 stars)
PR merge metrics
 (Avg merge 2m) (1 merged PR in 30d)

Description

As the complexity of the project grows, we find that often adding a change to QEMU configurations breaks something else unintended. This pretty much happens every single change and is becoming unmanageable. We need an actual test plan:

  1. A set of .utm files of various operating systems, architectures, and configurations.
  2. A checklist of things to test for each one (mouse, sound, network, etc)
  3. A matrix of configurations to check (Intel/M1 Mac, iPad, iOS of different versions, etc)

Then we can have a release sign-off that involves making sure everything is tested.

Contributor guide

Research direction
Create a set of .utm files for various OS and architectures, then define a checklist of features to test (mouse, sound, network) and a configuration matrix for different devices (Intel/M1 Mac, iPad, iOS versions). Start by examining existing test files in the repository for format and structure.
Tech stack
swift
Domain
frontendtesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
XcodeUTM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65