Cloudpods – Testing

Docs: Login Test Cases

Mon, 01 Jan 0001 00:00:00 +0000

Scope

Covers login, login security policies, logout, and session management of the OneCloud Web console. See the following product features:

Environment and account

Item	Value
Address	https://test.yunion.io
Account	cloudadmin
Password	cloudadmin@test
Domain	Default

Login page elements (the actual UI prevails): the Account login / Mobile number login tabs, username input box, password input box, login button, image captcha (shown according to policy), Specify login domain entry, Forgot password, and third-party/CAS login entry.

Case overview

Number	Case name	Priority	Type
TC-LOGIN-001	Log in with the correct username and password	P0	Positive
TC-LOGIN-002	Log in with a wrong password	P0	Negative
TC-LOGIN-003	Log in with a non-existent username	P1	Negative
TC-LOGIN-004	Submit with an empty username or password	P1	Validation
TC-LOGIN-005	Log in with a specified login domain	P1	Positive
TC-LOGIN-006	Login fails when the domain and user do not match	P2	Negative
TC-LOGIN-007	An image captcha appears after repeated wrong passwords	P1	Security
TC-LOGIN-008	Exceeding the wrong-password limit locks the account and generates a security alert	P1	Security
TC-LOGIN-009	A user with “Console login” disabled cannot log in	P1	Negative
TC-LOGIN-010	A disabled user cannot log in	P1	Negative
TC-LOGIN-011	Log in as a user with MFA enabled	P1	Positive
TC-LOGIN-012	A user with an expired password cannot log in	P2	Negative
TC-LOGIN-013	The landing view after login is correct	P0	Positive
TC-LOGIN-014	The session becomes invalid after logout	P0	Positive
TC-LOGIN-015	Accessing an inner page without logging in redirects to the login page	P1	Security
TC-LOGIN-016	Switch the language of the login page	P2	Positive
TC-LOGIN-017	Log in as an identity provider (LDAP) user	P2	Positive
TC-LOGIN-018	Login session validity period	P2	Security

Priority: P0

Prerequisites: The cloudadmin account is enabled and allowed to log in to the console.

Steps:

Open https://test.yunion.io in a browser.
On the “Account login” tab, enter the username cloudadmin.
Enter the password cloudadmin@test.
Click the “Login” button.

Expected results:

After submission, the UI shows a transitional state such as “Logging in, please wait”.
Login succeeds and jumps to the dashboard page, with the current user shown in the upper right corner.
The top area shows the view switch entry, and the current view is the Admin Console view.
A login credential (yunionauth) and the scope, domain, tenant, and other cookies are generated in the browser.
Entering the address again to access the console does not require logging in again.

Actual result: Pass (verified at the API layer; see Appendix B).

Priority: P0

Prerequisites: Same as TC-LOGIN-001.

Steps:

Open the login page.
Enter the username cloudadmin.
Enter the wrong password wrongpass123.
Click the “Login” button.

Expected results:

Login fails and stays on the login page.
The page prompts “Incorrect username or password” (the API returns incorrect username or password).
The password input box is cleared or kept as masked text; no plaintext is echoed.
No valid login credential is generated and the console cannot be entered.

Actual result: Pass. The API returns HTTP 401 with the response body {"class":"IncorrectUsernameOrPassword","code":401,"details":"incorrect username or password"}.

Priority: P1

Steps:

Open the login page.
Enter the username no_such_user_9999.
Enter any password.
Click the “Login” button.

Expected results:

Login fails.
The message is identical to TC-LOGIN-002 and does not distinguish “username does not exist” from “wrong password”, so that whether an account exists is not leaked.

Priority: P1

Steps:

Open the login page, leave both the username and password empty, and click the “Login” button.
Fill in only the username, leave the password empty, and click the “Login” button.
Fill in only the password, leave the username empty, and click the “Login” button.

Expected results:

In all three cases no login request is sent and the page stays where it is.
A validation message “Please enter the username” / “Please enter the password” appears below the corresponding input box.
The input box is highlighted in red or clearly shows an error state.

Priority: P1

Prerequisites: A user that is enabled and allowed to log in to the console exists in the Default domain.

Steps:

Open the login page and click the “Specify login domain” entry.
Select Default in the domain list.
Enter the username cloudadmin and the password cloudadmin@test.
Click the “Login” button.
In the user menu in the upper right corner of the console, reopen the login domain setting and click “Reset login domain”.

Expected results:

After specifying the login domain, the UI shows “Current login domain: Default”.
Login succeeds and the console opens.
After resetting the login domain, the login page returns to platform-level login and does not preselect any domain.

Priority: P2

Prerequisites: A domain that cloudadmin has not joined exists (for example a new domain testdomain).

Steps:

Open the login page, click “Specify login domain”, and select a domain that cloudadmin has not joined.
Enter the username cloudadmin and the password cloudadmin@test.
Click the “Login” button.

Expected results:

Login fails and prompts that the username or password is incorrect.
No cross-domain privilege escalation login occurs.

Priority: P1

Prerequisites: Confirm that a wrong-password threshold is configured on the platform (keystone service parameter password_error_lock_count; the default 0 means no locking). This case consumes cloudadmin’s error count; confirm the threshold with the administrator before executing it to avoid locking the account.

Steps:

Log in repeatedly with cloudadmin and a wrong password until the captcha input box appears in the UI.
Record the number of failures required to trigger the captcha.
Enter a wrong captcha in the captcha input box and click “Login”.
Enter the correct captcha and submit.

Expected results:

After the threshold is reached, an image captcha input box appears on the login page and the captcha image can be refreshed.
When the captcha is wrong, it prompts “Please enter a valid captcha” / “Incorrect captcha” and the login is rejected.
When the captcha is correct and the password is correct, login succeeds.

Remarks: If the captcha policy is not enabled on the platform, mark this case as “Not applicable” and record the platform configuration value.

Priority: P1

Prerequisites: password_error_lock_count is configured to a value greater than 0.

Steps:

Log in repeatedly with cloudadmin and a wrong password, exceeding the configured threshold.
Try to log in with the correct password.
Log in with an administrator account and view the security alert list.

Expected results:

After the threshold is exceeded, the account is locked; even the correct password cannot log in and a message says the account is locked.
A “Login anomaly” alert record is generated on the security alert page.
The alert is also sent to the locked user, the domain administrator of the user’s domain, and the system administrator.
After the lock is released, the correct password can log in normally.

Remarks: This case locks the cloudadmin account. Do not execute it in a production or shared environment; confirm that it can be unlocked before executing.

Priority: P1

Prerequisites: Prepare a local user that is enabled but has “Login to console” turned off.

Steps:

As an administrator, create a user in user management and turn off “Login to console”.
Log out of the current session and log in to the console with that user.

Expected results:

Login is rejected, prompting that there is no console login permission or that the username or password is incorrect.
The user can still access via the API and other means (if the platform allows it) but cannot log in to the console.

Priority: P1

Prerequisites: Prepare a user in the disabled state that is currently online.

Steps:

Log in to the console with that user and keep the session online.
As an administrator, disable the user in user management.
The user keeps operating on console pages.
The user logs out and logs in again.

Expected results:

The disable operation does not force an online user to log out immediately.
After the user logs out, logging in again fails and prompts that the user is disabled.
Logging in with the correct password of the disabled user also fails.

Priority: P1

Prerequisites: Two-factor authentication is enabled in the global configuration, and the target user has MFA enabled and has completed credential binding.

Steps:

Log in as a user with MFA enabled and enter the correct username and password.
Enter the 6-digit security code on the login protection page that appears.
Submit once with a wrong security code.
Submit with the correct security code.

Expected results:

After the password is verified, the console is not entered directly; instead a 6-digit security code is required.
A wrong security code prompts “Incorrect security code, please re-enter” and the console cannot be entered.
Submitting the correct security code enters the console successfully.

Remarks: On test.yunion.io, MFA is currently not enabled for cloudadmin (totp_on=false in the login credential). Executing this case requires preparing a user with MFA enabled first; if global two-factor authentication is not enabled, the user-side MFA switch does not take effect.

Priority: P2

Prerequisites: A user with an expired password exists.

Steps:

Expected results:

A user whose password has expired cannot log in to the system.
A user whose password expires in 7 days can log in normally, and after login is prompted that the password is about to expire and is advised to change it as soon as possible.

Priority: P0

Prerequisites: cloudadmin has the admin role of the system project in the Default domain.

Steps:

Log in as cloudadmin.
Check the view switch entry in the top area.
Switch to the Domain Admin Console view and the Project view in turn, then switch back to the Admin Console view.

Expected results:

The Admin Console view is the default landing view, where system-level resources can be seen.
The view switch entry is displayed normally, and the left navigation menu changes with the view after switching.
The Domain Admin Console view requires three-level permissions to be enabled on the platform; when not enabled, that view does not appear.

Priority: P0

Steps:

Log in to the console and record the current address.
Click the user icon in the upper right corner and select “Sign out”.
Use the browser back button to return to the page from before the logout.
Paste the inner page address from before the logout and access it directly.

Expected results:

After logout, the page jumps to the login page.
Going back or directly accessing the inner page is redirected to the login page and no business data is shown.
The login credential in the browser is invalid.

After a third-party identity provider (such as CAS) user logs out, if the session on the authentication server side is not destroyed, the user may be logged in again automatically. This is the behavior of the identity provider and needs to be confirmed separately.

Priority: P1

Steps:

Clear the browser cookies or use an incognito window.
Access an inner page address directly, such as a resource list address like /vminstance.

Expected results:

The request is intercepted and redirects to the login page.
After a successful login, the user is redirected back to the inner page address originally accessed (if the platform supports redirecting back).

Priority: P2

Steps:

Open the login page and switch the UI language to English.
Switch back to Simplified Chinese.

Expected results:

The login page text switches with the language; the login button, input box placeholders, and error messages are all in the target language.
Switching the language does not affect the username and password already entered.

Priority: P2

Prerequisites: An LDAP identity provider is configured and enabled on the platform, and users have been synced.

Steps:

On the login page, select the corresponding identity provider (for example, select the domain corresponding to the identity provider in “Specify login domain”).
Enter the username and password of the LDAP user and log in.

Expected results:

Identity provider users can log in to the console normally.
Users marked as from an LDAP identity provider in user management do not support resetting the password on the platform side.

Priority: P2

Steps:

Log in to the console and check the expiration time of the login credential cookie.
After the page stays idle beyond the credential validity period, operate on the page or access an inner page again.

Expected results:

The login credential validity period is 24 hours by default (Max-Age=86399).
After the credential expires, operating on the page or accessing an inner page redirects to the login page and requires logging in again.

Actual result: Pass. In the measured login response, the Max-Age of the four cookies yunionauth, scope, domain, and tenant is 86399 seconds.

Appendix A: API-layer verification script

Login-related UI behavior can be quickly regression tested with the login API. The following script performs API-level verification against https://test.yunion.io and can be copied and run directly (curl and python3 are required).

#!/bin/bash
# verify_login.sh — login API regression verification
BASE="https://test.yunion.io"
USER="cloudadmin"
PASS="cloudadmin@test"
DOMAIN="Default"

echo "== TC-LOGIN-001 Login with correct credentials =="
code=$(curl -s -o /tmp/login_ok.txt -w "%{http_code}" \
 -c /tmp/login_cookie.txt \
 -X POST -H 'Content-Type: application/json' \
 -d "{\"username\":\"$USER\",\"password\":\"$PASS\",\"domain\":\"$DOMAIN\"}" \
 "$BASE/api/v1/auth/login")
echo "HTTP $code"
if [ "$code" = "200" ]; then
 echo "PASS: login succeeded"
 grep -q yunionauth /tmp/login_cookie.txt && echo "PASS: yunionauth credential issued"
else
 echo "FAIL: expected 200, got $code"
fi

echo
echo "== TC-LOGIN-002 Login with wrong password =="
resp=$(curl -s -w "\n%{http_code}" \
 -X POST -H 'Content-Type: application/json' \
 -d "{\"username\":\"$USER\",\"password\":\"wrongpass123\",\"domain\":\"$DOMAIN\"}" \
 "$BASE/api/v1/auth/login")
body=$(echo "$resp" | head -n -1)
code=$(echo "$resp" | tail -n 1)
echo "HTTP $code"
echo "$body" | grep -q IncorrectUsernameOrPassword \
 && echo "PASS: returned IncorrectUsernameOrPassword" \
 || echo "FAIL: expected error class not returned"

echo
echo "== TC-LOGIN-003 Login with non-existent user (message should match wrong password) =="
resp=$(curl -s -w "\n%{http_code}" \
 -X POST -H 'Content-Type: application/json' \
 -d "{\"username\":\"no_such_user_9999\",\"password\":\"whatever\",\"domain\":\"$DOMAIN\"}" \
 "$BASE/api/v1/auth/login")
body=$(echo "$resp" | head -n -1)
code=$(echo "$resp" | tail -n 1)
echo "HTTP $code"
echo "$body" | grep -q IncorrectUsernameOrPassword \
 && echo "PASS: same response as wrong password; account existence not leaked" \
 || echo "FAIL: error class differs from wrong password"

echo
echo "== TC-LOGIN-018 Session validity period =="
exp=$(curl -s -D - -o /dev/null \
 -X POST -H 'Content-Type: application/json' \
 -d "{\"username\":\"$USER\",\"password\":\"$PASS\",\"domain\":\"$DOMAIN\"}" \
 "$BASE/api/v1/auth/login" | grep -i '^set-cookie: yunionauth' | grep -o 'Max-Age=[0-9]*')
echo "yunionauth $exp"
[ "$exp" = "Max-Age=86399" ] && echo "PASS: validity period is 24 hours" || echo "WARN: validity period differs from expected 86399"

After a successful login, you can use the credential in /tmp/login_cookie.txt to call other service APIs, for example:

curl -s -b /tmp/login_cookie.txt "$BASE/api/v1/servers?limit=5"

Appendix B: Measured records for this environment

The following API behavior was confirmed by measurement on https://test.yunion.io (2026-09-15) and can serve as the baseline for the expected results of the cases.

Check item	Measured result
Console reachability	HTTP 200, HTTP/2, nginx
Login API	`POST /api/v1/auth/login`, request body `{"username","password","domain"}`
Correct credentials	HTTP 200, empty response body, issues `yunionauth`/`scope`/`domain`/`tenant` cookies
Wrong password	HTTP 401, `{"class":"IncorrectUsernameOrPassword","details":"incorrect username or password"}`
cloudadmin default scope	`system` (Admin Console view)
cloudadmin default domain	`Default`
cloudadmin MFA status	Not enabled (`totp_on=false`, `totp_verified=false` in the credential)
Login credential validity period	86399 seconds (24 hours)
Image captcha API	`GET /api/v1/auth/captcha`, returns `image/png` and issues a `captcha` cookie

Note: The above are API-layer measurement conclusions; cases that depend on UI interaction (such as when the captcha appears, MFA interaction, and password expiration prompts) still need to be executed step by step in a browser to confirm.

Docs: VM Creation Test Cases

Mon, 01 Jan 0001 00:00:00 +0000

Scope

Covers the configuration of each parameter when creating a VM and the verification of the creation result. For parameter meanings, see Create a VM; for operations after creation, see Instance operations and View details.

Entry points (see the “Entry points” section of the guide):

Create a Local IDC VM: On the VM instance page, click the “Create” button above the list;
Create a private cloud VM: Click the “Private cloud” tab at the top, then click the “Create” button;
Create a public cloud VM: Click the “Public cloud” tab at the top, then click the “Create” button.

On any VM creation page, you can use the “Local IDC”, “Private cloud”, and “Public cloud” tabs at the top to switch the platform to create on.

Environment check

Before executing the cases, check each item in this section. If any item is not satisfied, the corresponding cases cannot pass (in that case record them as “Blocked” rather than “Failed”).

Local IDC

An OneCloud platform host in the enabled and online state exists in basic resources, or the cloud management platform is integrated with VMware and a VMware host in the enabled state exists;
An available IP subnet with the “guest” attribute exists in the target zone;
A public image or custom image in the “available” state exists in the system image list.

Private cloud

The cloud management platform has imported the resources of an OpenStack, ZStack, ZettaCloud, or HCSO cloud account;
A host in the enabled state belonging to one of the above platforms exists in basic resources;
The corresponding platform has an available IP subnet.

Public cloud

The cloud management platform has imported an Alibaba Cloud, AWS, Azure, Huawei Cloud, Tencent Cloud, or UCloud cloud account;
The cloud account is enabled, healthy, and has sufficient balance;
A VPC and IP subnet exist in the corresponding platform region.

For the check results, refer to the measured data in “Appendix A: Measured snapshot of resources in this environment” of this document.

Case overview

Number	Case name	Priority	Platform
TC-VM-001	Create a Linux VM on Local IDC (minimum required parameters)	P0	Local IDC
TC-VM-002	Create multiple VMs in batch and name them by sequence number	P0	Local IDC
TC-VM-003	Use the ordered suffix placeholder # for naming	P2	Local IDC
TC-VM-004	Name with a hostname expression	P2	Local IDC
TC-VM-005	Specify an IP subnet and configure a static IP manually	P1	Local IDC
TC-VM-006	Administrator password generated randomly and viewed in the list	P0	Local IDC
TC-VM-007	Associate the administrator password with a key	P1	Local IDC
TC-VM-008	Add data disks	P1	Local IDC
TC-VM-009	Bind an elastic public IP in advanced configuration	P2	Local IDC
TC-VM-010	Bind a security group in advanced configuration	P2	Local IDC
TC-VM-011	Combination of remote console protocol and graphics card	P2	Local IDC
TC-VM-012	Create from a Windows image and connect remotely	P1	Local IDC
TC-VM-013	Create a VM by booting from ISO	P2	Local IDC
TC-VM-014	Custom data (cloud-init)	P2	Local IDC
TC-VM-015	Create a VM from an ARM architecture image	P2	Local IDC
TC-VM-016	Create a VM on the ZStack platform	P1	Private cloud
TC-VM-017	Create a VM on the OpenStack platform	P1	Private cloud
TC-VM-018	Create a pay-as-you-go VM on Alibaba Cloud	P1	Public cloud
TC-VM-019	Public cloud subscription and expire-and-release	P2	Public cloud
TC-VM-020	Validation of required fields and invalid values	P0	General
TC-VM-021	Duplicate VM name	P1	General
TC-VM-022	Creation fails when no host or IP subnet is available	P1	General
TC-VM-023	Status transitions during creation	P0	General
TC-VM-024	Lifecycle operations and deletion after creation	P0	General

TC-VM-001 Create a Linux VM on Local IDC (minimum required parameters)

Priority: P0

Prerequisites: An online host and an available IP subnet exist in Local IDC, and an available Linux public image exists in the image list.

Steps:

Log in as cloudadmin and go to the “Resource Management/Compute/Instances/VM instance” page.
Click the “Local IDC” tab at the top, then click the “Create” button above the list.
Basic configuration: Select the default region, and select a zone with an online host.
Set the name, for example tc-vm-001.
Instance configuration: Keep the quantity at 1, and select “OneCloud” as the platform.
Spec configuration: Select 1 CPU core and 1G memory (or select “Unlimited” and pick the smallest instance type).
Image configuration: Select a Linux image from public images for the operating system, for example openEuler-Linux-24.03 LTS SP4-x86_64.
System disk: Select the default disk type, with a size not lower than the image’s minimum disk requirement.
Login configuration: Select “Random” for the administrator password.
Network configuration: Select “Auto schedule” for the network or specify an available IP subnet.
Click the “Create” button.

Expected results:

After clicking “Create”, a creation success message appears and the page returns to the VM instance list.
The newly created VM appears in the list with the name tc-vm-001.
The VM status transitions from “Creating” to “Running”.
The region, zone, image, and spec of the VM are consistent with the submitted configuration.

TC-VM-002 Create multiple VMs in batch and name them by sequence number

Priority: P0

Steps:

Follow the steps of TC-VM-001 to open the create page, and set the name to tc-batch.
Set the quantity to 3 in the instance configuration.
Keep the other parameters the same as TC-VM-001 and click the “Create” button.

Expected results:

After a successful creation, 3 VMs appear in the list.
The first VM is named tc-batch and the rest are tc-batch-1 and tc-batch-2 (when the quantity is greater than 1, all names except the first are expressed as name-1~N).
All 3 VMs transition to “Running” normally.
The IP addresses allocated to the 3 VMs do not conflict with each other.

TC-VM-003 Use the ordered suffix placeholder # for naming

Priority: P2

Steps:

Open the create page and set the name to tc-host##.
Set the quantity to 2.
Keep the other parameters at their defaults and click the “Create” button.

Expected results:

The created VMs are named tc-host00 and tc-host01 (each # occupies one position).
The sequence number is zero-padded according to the number of placeholder digits.

TC-VM-004 Name with a hostname expression

Priority: P2

Steps:

Open the create page and set the name to ${region}-${zone}.
Keep the other parameters at their defaults and click the “Create” button.
Create another VM with the name ${host}.

Expected results:

The name is evaluated from the expression and displayed as “region name-zone name”.
Variable names must be lowercase; when ${host} is used, it is displayed as the name of the host that creates the VM.
Variables in the expression take values according to “Hostname expression examples” in the guide; unsupported variable names do not take effect or are output as-is.

TC-VM-005 Specify an IP subnet and configure a static IP manually

Priority: P1

Prerequisites: An available IP subnet exists in the target zone and the subnet has unallocated IPs.

Steps:

Open the create page and select “Specify IP subnet” in “Network configuration”.
Select a VPC and an IP subnet.
Click the “Configure IP manually” button and fill in an unoccupied IP address within the subnet range.
Click “OK” to save the IP configuration.
After configuring the other parameters, click the “Create” button.

Expected results:

The IP filled in the “Configure IP manually” dialog is saved correctly and echoed back.
After the VM is created successfully, its IP address is consistent with the manually specified address.
When a second VM is created repeatedly with the same IP, creation fails or prompts that the IP is already in use.

TC-VM-006 Administrator password generated randomly and viewed in the list

Priority: P0

Steps:

Open the create page and select “Random” for the administrator password in “Login configuration”.
After configuring the other parameters, click the “Create” button.
After a successful creation, find the VM in the VM instance list and check the “Password” column.
Copy the password and use it to log in to the VM via VNC or a remote connection.

Expected results:

“Random” does not show the plaintext password; after creation, the administrator password can be viewed and copied in the Password column of the VM instance list.
The administrator account is root for Linux systems and administrator for Windows systems.
The copied password can be used to log in to the VM successfully.

TC-VM-007 Associate the administrator password with a key

Priority: P1

Prerequisites: At least one keypair already exists.

Steps:

In “Login configuration”, select “Associate key” for the administrator password.
Select an existing key.
After configuring the other parameters, click the “Create” button.
After a successful creation, log in to the VM over SSH with the corresponding private key.
When no key has been created, try to select “Associate key”.

Expected results:

After a key is associated, the VM must be logged in to remotely with the private key, not with a password.
The matching private key can be used to log in successfully.
When no key has been created, “Associate key” cannot be selected or prompts that a key must be created first.

TC-VM-008 Add data disks

Priority: P1

Steps:

Confirm the disk type and size in the system disk area of “Disk configuration”.
In the “Data disks” area, click add and set the disk type, medium, and size.
Add another data disk (optional).
After configuring the other parameters, click the “Create” button.
After a successful creation, view the disk information on the VM details page.

Expected results:

Data disks are optional and multiple disks can be added; the disk type is the same as the system disk.
Only the first data disk supports selecting a disk type; the type of subsequently added data disks is the same as the first one.
After a successful creation, the disk list on the details page contains all configured disks, with sizes consistent with the configuration.
Data disks are attached to the VM but are not partitioned automatically; they must be partitioned manually after logging in.

TC-VM-009 Bind an elastic public IP in advanced configuration

Priority: P2

Prerequisites: An available EIP line is configured on the platform.

Steps:

Expand “Advanced configuration” and select “Create” in “Elastic public IP”.
Select the line type, select “By bandwidth” for the network billing method, and set the bandwidth (for example 1Mbps).
After configuring the other parameters, click the “Create” button.
After a successful creation, view the EIP information of the VM.

Expected results:

The EIP is created and bound successfully together with the VM.
The bound EIP and bandwidth configuration can be seen in the VM details.
With bandwidth billing, traffic exceeding the bandwidth is dropped (this can be verified with an actual transfer).

TC-VM-010 Bind a security group in advanced configuration

Priority: P2

Prerequisites: An available security group and its rules exist.

Steps:

Expand “Advanced configuration” and select 1 security group in “Security group”.
Try to select more than 5 security groups.
After configuring the parameters (without exceeding the limit), click the “Create” button.

Expected results:

Security groups can be bound to a VM, up to 5. Beyond that, selection cannot continue or a clear message is shown.
After binding, the security group rules take effect: ports that are not allowed are inaccessible and allowed ports are accessible.

TC-VM-011 Combination of remote console protocol and graphics card

Priority: P2

Prerequisites: A OneCloud platform VM.

Steps:

Expand “Advanced configuration”, select VNC for “Remote console protocol”, and try Standard and QXL for “Graphics card” in turn.
Change “Remote console protocol” to SPICE and observe the available options of “Graphics card”.
Save and create the VM, then open the remote console of the VM.

Expected results:

With the VNC protocol, the graphics card can be Standard or QXL.
With the SPICE protocol, the graphics card can only be QXL.
The remote console opens normally and displays the VM screen.

Remarks: VNC has no audio or USB transfer and is not suitable for virtual desktops; SPICE performs better in color, audio, and USB and is suitable for virtual desktops.

TC-VM-012 Create from a Windows image and connect remotely

Priority: P1

Steps:

Open the create page and select a Windows image for the operating system (for example windows_server_2022_...qcow2).
Set the system disk size to be not lower than the image’s minimum disk requirement.
Select “Random” for the administrator password.
After configuring the other parameters, click the “Create” button.
After a successful creation, copy the administrator password in the list and open the remote console connection.
Log in with the administrator account and the copied password.

Expected results:

The VM is created successfully and enters the “Running” state.
The remote console can display the Windows login screen normally.
The administrator account and the copied password can be used to log in successfully.
If Windows is installed by mounting an ISO, Virtio drivers need to be installed separately after installation (the drivers are available in Image Marketplace - ISO).

TC-VM-013 Create a VM by booting from ISO

Priority: P2

Prerequisites: An image in ISO format exists in the image list.

Steps:

Open the create page, select “Boot from ISO” for the operating system, and select an ISO image.
Check the “Login configuration” area.
After configuring the other parameters, click the “Create” button.
After a successful creation, open the remote console and install the operating system.

Expected results:

After “Boot from ISO” is selected, setting an administrator password is not supported, and a message says it must be set while installing the operating system.
All disk types are displayed as “data disk” (the display does not affect normal use).
The remote console can enter the ISO boot installation interface.
Only the OneCloud and VMware platforms support booting from ISO.

TC-VM-014 Custom data (cloud-init)

Priority: P2

Steps:

Expand “Advanced configuration” and enter a shell script (for example creating a file and writing the host name) as text in “Custom data”.
After configuring the parameters, click the “Create” button.
After a successful creation, log in to the VM and check the script execution result.
Submit the configuration again using “Upload JSON file”.

Expected results:

Both the text method and the uploaded JSON file method can submit the configuration.
The OneCloud platform supports shell, python, and perl scripts; private cloud and public cloud platforms support shell and yaml scripts.
The script is executed after the VM starts for the first time, and the check result matches the expectation of the script.

TC-VM-015 Create a VM from an ARM architecture image

Priority: P2

Prerequisites: An ARM architecture host and an ARM architecture image exist.

Steps:

Open the create page and select ARM for “CPU architecture”.
Check the operating system image list.
Select UEFI for the boot mode and try to select BIOS.
After configuring the parameters, click the “Create” button.

Expected results:

Only the OneCloud platform supports the ARM architecture; this option is unavailable on other platforms.
When the CPU architecture is ARM, the image list is filtered by architecture and shows only ARM architecture images.
The ARM architecture supports the UEFI boot mode only and BIOS cannot be selected.

TC-VM-016 Create a VM on the ZStack platform

Priority: P1

Prerequisites: The cloud management platform has imported ZStack resources, and an online host and an available IP subnet exist in the ZStack region.

Steps:

Go to the VM instance page and click the “Private cloud” tab at the top.
Click the “Create” button, then click the “Private cloud” tab at the top.
Select the region and zone corresponding to ZStack (the region determines the platform the VM belongs to).
Set the name, and select a spec and a ZStack platform image.
Select an available IP subnet in the network configuration.
Click the “Create” button.

Expected results:

The VM is created successfully on the ZStack platform and enters the “Running” state.
The platform displayed for the VM in the list is ZStack.
The VM can be accessed normally through the remote console and SSH.

TC-VM-017 Create a VM on the OpenStack platform

Priority: P1

Prerequisites: The cloud management platform has imported OpenStack resources, and an online host and an available IP subnet exist in the region.

Steps:

Under the “Private cloud” tab, select the region and zone corresponding to OpenStack.
Select an image as the system disk (OpenStack supports using an image as the system disk, with image storage as the system disk storage).
After the system disk is configured, try to set the data disk type.
After configuring the network and other parameters, click the “Create” button.

Expected results:

The VM is created successfully on the OpenStack platform and enters the “Running” state.
When the system disk uses image storage, the data disk type can be set.
The region, platform, and spec of the VM are consistent with the submitted configuration.

TC-VM-018 Create a pay-as-you-go VM on Alibaba Cloud

Priority: P1

Prerequisites: An available Alibaba Cloud cloud account with sufficient balance has been imported, and a VPC and IP subnet exist in the corresponding region.

Steps:

Go to the VM instance page, click the “Public cloud” tab at the top, then click the “Create” button.
Select “Pay-as-you-go” for the billing method.
Determine the available instance types by geography, platform, region, and zone, and select Alibaba Cloud and a nearby region.
Select an image that already has a cached badge (to avoid a long image caching time).
Select a VPC and IP subnet, and configure the other parameters.
Click the “Create” button.

Expected results:

The VM is created successfully on Alibaba Cloud and synced to the cloud management platform, with the status “Running”.
Charges are billed by actual usage.
When an uncached image is used, creation takes longer; when a cached badge appears next to the image name, creation is faster.
On public clouds, only pay-as-you-go VMs support “Expire and release”.

TC-VM-019 Public cloud subscription and expire-and-release

Priority: P2

Prerequisites: A domestic public cloud cloud account.

Steps:

Create a VM under the “Public cloud” tab and select “Subscription” for the billing method.
Check whether “Auto-renewal” can be selected, and set the purchase duration.
Switch the billing method to “Pay-as-you-go” and set “Expire and release” to “1 hour”.
After configuring the parameters, click the “Create” button.

Expected results:

Subscription is a prepaid mode and supports selecting auto-renewal.
Only domestic public clouds support subscription; only Alibaba Cloud subscription supports purchasing one week, and when one week is selected the platform automatically selects Alibaba Cloud.
For Alibaba Cloud weekly purchases, the renewal period is one week; monthly is one month and yearly is one year; the renewal period of other platforms is one month.
Expire and release is supported only for pay-as-you-go VMs; when the time is exceeded, the VM is deleted and moved to the recycle bin.
After being moved to the recycle bin, charges still apply, and the VM must be purged from the recycle bin.

TC-VM-020 Validation of required fields and invalid values

Priority: P0

Steps:

Open the create page and click the “Create” button directly without filling in anything.
Fill in the required items such as region, name, spec, image, and network one by one, and resubmit after each item is filled in to observe how the message changes.
Fill in invalid characters in the name (such as spaces and special characters like /).
Fill in a system disk size smaller than the image’s minimum disk size.
Fill in CPU cores or memory that exceed the remaining resources of the host.

Expected results:

When required fields are missing, the submission is intercepted, the corresponding fields are highlighted in red, and a “Please enter/Please select xxx” message is shown.
The submission cannot succeed until all required fields are filled in.
An invalid name is intercepted with a clear message.
When the system disk size is smaller than the image’s minimum disk requirement, the submission is not allowed or a message is shown.
When the spec exceeds the available resources, the spec cannot be selected, or the submission fails with the reason given.

TC-VM-021 Duplicate VM name

Priority: P1

Prerequisites: A VM named tc-dup already exists.

Steps:

Create a VM and fill in the name tc-dup, which already exists.
After configuring the other parameters, click the “Create” button.

Expected results:

The creation is rejected and prompts that the name already exists.
VMs and Baremetals share a name namespace, so trying to create a VM with the name of an existing Baremetals resource is likewise rejected.
Names are unique in the system.

TC-VM-022 Creation fails when no host or IP subnet is available

Priority: P1

Prerequisites: Prepare a zone with no online host, or a subnet whose IPs are exhausted/unavailable.

Steps:

Create a VM and select a zone that has no online host.
After configuring the other parameters, click the “Create” button.
Then select a scenario where the host is online but the IP subnet does not meet the conditions and submit again.

Expected results:

When no host is available, creation fails and prompts that no host is available or that scheduling failed.
When no IP subnet is available, no subnet can be selected in the network configuration, or the submission fails with the reason given.
If the host request workflow (ticket) is enabled on the platform, a ticket request is initiated after parameter validation passes, and automatic deployment starts only after approval; when it is not enabled, the VM is created directly.

TC-VM-023 Status transitions during creation

Priority: P0

Steps:

Create a VM and observe the status in the list immediately after clicking “Create”.
Check the status count statistics in the upper right of the VM instance list.
Keep observing until the status no longer changes.
Open the details page of the VM and check each item of information.

Expected results:

After submission, the VM first appears in the list with the “Creating” status.
After a successful creation, the status transitions to “Running”; when creation fails, it is “Operation failed”.
The upper right of the list shows the total number of VMs and the number of VMs in the running, stopped, operation failed, and unknown states, and updates in real time as the status changes.
The name, region, zone, spec, image, IP, disk, and other information on the details page are consistent with the submitted configuration.

TC-VM-024 Lifecycle operations and deletion after creation

Priority: P0

Prerequisites: TC-VM-001 has been completed and a VM in the “Running” state exists.

Steps:

Select the VM in the VM instance list and perform “Stop”.
After confirming the stop, perform “Start”.
Perform “Restart”.
Perform “Delete”.
After deletion, view it in the recycle bin and perform purge.

Expected results:

After the stop operation, the status becomes “Stopped”; after the start, it returns to “Running”.
The remote console connection is interrupted during the restart; if “Force restart” is selected, unsaved data in the VM will be lost.
After deletion, the VM enters the recycle bin and is no longer shown in the list by default.
The deleted VM can be seen in the recycle bin and is permanently deleted after purge.
Public cloud VMs may still incur charges after being moved to the recycle bin, so purge them promptly when they are no longer used.

Appendix A: Measured snapshot of resources in this environment

The following data was obtained by measurement on https://test.yunion.io (2026-09-15) and is used for checking the prerequisites of the cases and as a reference for parameter values. Resource names differ in other environments; when executing, replace them with the actual options in the drop-down lists.

Local IDC

Item	Measured value
Region	`default` (Beijing OneCloud)
Zone	`Wangjing`, `yunion`, `test`
Online hosts (OneCloud/KVM)	`test-69-onecloud01` (40C/257923MB), `test-66-onecloud02` (40C/257755MB), `ampere-10-127-100-7-10-127-100-7` (32C/65079MB), `test-d2000-01-10-127-100-8` (8C/15929MB)
Online hosts (VMware/ESXi)	`10-127-40-2` (48C/131008MB), `10-127-40-4` (24C/98258MB)
Offline hosts	`esxi2`, `bm15`, `vbm1`, `vbm2`
guest IP subnets (examples)	`default-86` (10.206.0.1 ~ 10.206.15.254, gateway 10.206.0.1), `default-85`, `default-84`, and so on, one per VPC

Private cloud

Platform	Region	Zone	Online host	Available IP subnet
ZStack	`zs-test`	`ZONE-test`, `zone2`	`Host-test` (12C/11824MB)	Yes (about 50 subnets per zone)
OpenStack	`ops-test-RegionOne`	`nova`	`test-72-openstack01` (40C/262050MB)	Yes (about 50 subnets)

Available images (examples)

Type	Image name	Architecture	Minimum disk
Public image	`openeuler-24.03-lts-sp4-x86_64`	x86_64	40GB
Public image	`openEuler-Linux-24.03 LTS SP2-x86_64`	x86_64	40GB
Public image	`Kylin-Server-10-SP2-aarch64-Release-Build09-20231122.qcow2`	aarch64	—
Other	`CentOS-Linux-7.9-x86_64-2009`	x86_64	8GB
Other	`Debian-Linux-14 (Forky)-x86_64-latest`	x86_64	3GB
Other	`windows_server_2022_updated_july_2026_x86_64_20260820.qcow2`	x86_64	—
Other	`windows_11_pro_26h1_x86_64_20260816.qcow2`	x86_64	80GB

Public images (is_public=true) are shown in the “Public image” group of the drop-down list; the other items are mostly custom images or host images, selected by their actual groups.

Existing VMs

VMs such as qj-ubuntu-tmp, qj-test-w22, test-rocky, and glb-test-4.0.4 already exist in the environment; avoid these names when executing cases related to name uniqueness.

Appendix B: API-layer verification

The resource status during creation can be checked quickly through the API. First run verify_login.sh to obtain a login credential (see Appendix A of Login test cases), then:

BASE="https://test.yunion.io"
COOKIE=/tmp/login_cookie.txt

# View the VM list and status
curl -s -b $COOKIE "$BASE/api/v1/servers?limit=20" \
 | python3 -c "import sys,json;[print(s['name'],s['status'],s.get('hypervisor')) for s in json.load(sys.stdin)['data']]"

# View online hosts (check of creation prerequisites)
curl -s -b $COOKIE "$BASE/api/v1/hosts?limit=50" \
 | python3 -c "import sys,json;[print(h['name'],h['host_type'],h['host_status']) for h in json.load(sys.stdin)['data']]"

# View available IP subnets (check of creation prerequisites)
curl -s -b $COOKIE "$BASE/api/v1/networks?server_type=guest&limit=20" \
 | python3 -c "import sys,json;[print(n['name'],n['guest_ip_start'],n['guest_ip_end']) for n in json.load(sys.stdin)['data']]"

# View the image list
curl -s -b $COOKIE "$BASE/api/v1/images?limit=20" \
 | python3 -c "import sys,json;[print(i['name'],i.get('os_arch'),i.get('disk_format')) for i in json.load(sys.stdin)['data']]"

The correspondence between the status values in the API and the UI statuses: running = Running, ready = Stopped, start_fail/create_fail = Operation failed. The API layer is only used for quickly checking the environment and status; UI interaction, parameter validation messages, and the ticket workflow still need to be executed step by step in a browser according to the cases.

Docs: Test Cases

Mon, 01 Jan 0001 00:00:00 +0000

This directory maintains test cases for core features of the OneCloud Web console, used for feature verification and version regression. The cases are written based on the feature descriptions in the Web Console Guide, and the steps and parameter meanings are consistent with the guide.

Test environment

Test cases are executed in the following environment by default. If you execute them in another environment, first adjust the parameters in the cases according to the “Environment differences” section below.

Item	Value
Console address	https://test.yunion.io
Administrator account	cloudadmin
Administrator password	cloudadmin@test
Default domain	Default
Default view	Admin Console view (cloudadmin is the admin of the system project in the Default domain)
Local IDC region	Default (Beijing OneCloud)
Local IDC zones	test, yunion, Wangjing

Case numbering rules

Case numbers use the format TC-<module>-<sequence>:

TC-LOGIN-xxx: Cases related to login and logout; see Login.
TC-VM-xxx: Cases related to VM creation; see Create a VM.

Priority descriptions:

Priority	Meaning
P0	Smoke cases; must be tested on every release
P1	Main feature cases; must be tested in version regression
P2	Boundary and combination scenarios; executed as needed

General conventions

Prerequisites

Before executing any case, the following must be satisfied:

The browser can access the console address and load the login page normally;
The cloudadmin account can log in normally;
A host in the online state exists in the Local IDC region (otherwise the cases that create VMs cannot pass);
An available IP subnet exists in the Local IDC region (otherwise no network can be selected in the network configuration).

For how to check items 3 and 4, see the “Environment check” section of Create a VM.

Result recording

After each case is executed, record the following in “Actual result”:

Conclusion: Pass / Fail / Blocked;
Actual behavior: when it differs from the expected result, record the original text of the interface message;
Screenshot or API response: required for failed cases;
Executor, execution time, and the version under test.

Environment differences

The resource names in the cases (image name, IP subnet name, host name) are taken from the measured snapshot of test.yunion.io. These names are most likely different in other environments; when executing, replace them with the options actually available in the drop-down lists. This does not affect the acceptance criteria of the cases.

Case list

Login: Login, login security, logout and session — 18 cases in total.
Create a VM: Creating VMs on Local IDC, private cloud, and public cloud and various parameter combinations — 24 cases in total.

Cloudpods – Testing

Docs: Login Test Cases

Scope

Environment and account

Case overview

TC-LOGIN-001 Log in with the correct username and password

TC-LOGIN-002 Log in with a wrong password

TC-LOGIN-003 Log in with a non-existent username

TC-LOGIN-004 Submit with an empty username or password

TC-LOGIN-005 Log in with a specified login domain

TC-LOGIN-006 Login fails when the domain and user do not match

TC-LOGIN-007 An image captcha appears after repeated wrong passwords

TC-LOGIN-008 Exceeding the wrong-password limit locks the account and generates a security alert

TC-LOGIN-009 A user with “Console login” disabled cannot log in

TC-LOGIN-010 A disabled user cannot log in

TC-LOGIN-011 Log in as a user with MFA enabled

TC-LOGIN-012 A user with an expired password cannot log in

TC-LOGIN-013 The landing view after login is correct

TC-LOGIN-014 The session becomes invalid after logout

TC-LOGIN-015 Accessing an inner page without logging in redirects to the login page

TC-LOGIN-016 Switch the language of the login page

TC-LOGIN-017 Log in as an identity provider (LDAP) user

TC-LOGIN-018 Login session validity period

Appendix A: API-layer verification script

Appendix B: Measured records for this environment

Docs: VM Creation Test Cases

Scope

Environment check

Local IDC

Private cloud

Public cloud

Case overview

TC-VM-001 Create a Linux VM on Local IDC (minimum required parameters)

TC-VM-002 Create multiple VMs in batch and name them by sequence number

TC-VM-003 Use the ordered suffix placeholder # for naming

TC-VM-004 Name with a hostname expression

TC-VM-005 Specify an IP subnet and configure a static IP manually

TC-VM-006 Administrator password generated randomly and viewed in the list

TC-VM-007 Associate the administrator password with a key

TC-VM-008 Add data disks

TC-VM-009 Bind an elastic public IP in advanced configuration

TC-VM-010 Bind a security group in advanced configuration

TC-VM-011 Combination of remote console protocol and graphics card

TC-VM-012 Create from a Windows image and connect remotely

TC-VM-013 Create a VM by booting from ISO

TC-VM-014 Custom data (cloud-init)

TC-VM-015 Create a VM from an ARM architecture image

TC-VM-016 Create a VM on the ZStack platform

TC-VM-017 Create a VM on the OpenStack platform

TC-VM-018 Create a pay-as-you-go VM on Alibaba Cloud

TC-VM-019 Public cloud subscription and expire-and-release

TC-VM-020 Validation of required fields and invalid values

TC-VM-021 Duplicate VM name

TC-VM-022 Creation fails when no host or IP subnet is available

TC-VM-023 Status transitions during creation

TC-VM-024 Lifecycle operations and deletion after creation

Appendix A: Measured snapshot of resources in this environment

Local IDC

Private cloud

Available images (examples)

Existing VMs

Appendix B: API-layer verification

Docs: Test Cases

Test environment

Case numbering rules

General conventions

Prerequisites

Result recording

Environment differences

Case list