Patricklang (talk | contribs) ((Work in progress) Test Day Page for Fedora in Windows Subsystem for Linux) |
Patricklang (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= Description = | = Description = | ||
{{{description|A brief description of the functionality being tested.}}} | {{{description|A brief description of the functionality being tested.}}} | ||
<noinclude> | <noinclude> | ||
In Fedora 42, a new image is being built that's intended to use with Windows Subsystem for Linux. This will allow users to have a simple, easy to set up Fedora environment for development and testing use. WSL manages a lightweight VM with Wayland, PulseAudio, and some extra filesystem mounts provided. The user's choice of distro, such as Fedora, is run in an isolated namespace with its own root image. Multiple distributions may be run side by side in different namespaces, sharing the same kernel. | |||
The Fedora changes are fully described at [Changes/FedoraWSL] | |||
= Setup ''(optional)'' = | = Setup ''(optional)'' = | ||
Optionally provide instructions to prepare the test environment. | Optionally provide instructions to prepare the test environment. | ||
Revision as of 00:00, 30 January 2025
Description
A brief description of the functionality being tested.
In Fedora 42, a new image is being built that's intended to use with Windows Subsystem for Linux. This will allow users to have a simple, easy to set up Fedora environment for development and testing use. WSL manages a lightweight VM with Wayland, PulseAudio, and some extra filesystem mounts provided. The user's choice of distro, such as Fedora, is run in an isolated namespace with its own root image. Multiple distributions may be run side by side in different namespaces, sharing the same kernel.
The Fedora changes are fully described at [Changes/FedoraWSL]
Setup (optional)
Optionally provide instructions to prepare the test environment.
How to test
Be as specific as required for the target audience.
- Start here ...
- Next do this ...
- Finally click that
Expected Results
The following must be true to consider this a successful test run. Be brief ... but explicit.
- Step #1 completes without error
- The system boots into runlevel 5
- Program completes with exit code 0
Optional (optional)
Optionally provide hints for exploratory testing.
