From Fedora Project Wiki
(update test case for newUI (can't add incomplete supplementary repos any more, so just test specifying a full repo)) |
No edit summary |
||
Line 6: | Line 6: | ||
# Click the ''On the network'' radio button and change the drop-down to ''http://'' or ''ftp://'' | # Click the ''On the network'' radio button and change the drop-down to ''http://'' or ''ftp://'' | ||
# Complete the URL of your desired repository in the text entry field - e.g. download.fedoraproject.org/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/x86_64/os/ | # Complete the URL of your desired repository in the text entry field - e.g. download.fedoraproject.org/pub/fedora/linux/development/{{FedoraVersionNumber|next}}/x86_64/os/ | ||
# If you have a proxy, configure | # If you have a proxy, configure it by clicking on ''Proxy setup...'' | ||
# Configure partitioning in a normal way and complete the installation | # Configure partitioning in a normal way and complete the installation | ||
|results= | |results= |
Revision as of 01:28, 18 October 2012
Description
This test case verifies selection of a specific HTTP(or FTP)-based package repository through graphical repository dialog during installation. Testing also includes verifying proper installation of packages included in the repository.
How to test
- Boot the installer using any available non-live means (
netinst.iso
, pxeboot images orDVD.iso
) - Enter the Installation Source screen
- Click the On the network radio button and change the drop-down to http:// or ftp://
- Complete the URL of your desired repository in the text entry field - e.g. download.fedoraproject.org/pub/fedora/linux/development/42/x86_64/os/
- If you have a proxy, configure it by clicking on Proxy setup...
- Configure partitioning in a normal way and complete the installation
Expected Results
- The package metadata from the HTTP (or FTP) repository is read correctly
- Installation completes and system reboots successfully
- The repository selected is actually used for installation: this can be checked by examining the
packaging.log
log file