ARTICLE DETAIL

资讯详情

深耕网站建设与运营推广的一线实战洞察。

openBMC功耗封顶GUI测试

openBMC功耗封顶GUI测试 一 概述test_resource_management_menu中当前仅有2个测试用例一个导航测试一个设置封顶数值测试。变量分析变量主要是 XPath 定位器变量作用${xpath_resource_management_menu}左侧导航 Resource Management 菜单${xpath_resource_management_power_menu}Power 子菜单${xpath_resource_management_header}页面标题要求包含 “Power”${xpath_power_tab_power_consumption}当前功耗区域${xpath_power_cap_setting}Power cap setting 区域${xpath_power_cap_apply}Apply power cap 标签${xpath_power_cap_checkbox}Power cap 开关复选框${xpath_asset_tag_save_button}Save 按钮${xpath_power_cap_value}Power cap 数值输入框对应如下关键字Suite Setup Execution Launch Browser And Login GUI Navigate To Required Sub Menu ${xpath_resource_management_menu} ${xpath_resource_management_power_menu} power套件初始化流程调用Launch Browser And Login GUI启动浏览器并登录 GUI。调用Navigate To Required Sub Menu进入 Resource Management → Power 页面。最后一个参数power用于校验当前页面标题具体实现依赖gui_resource.robot。二、测试用例讲解用例 1Verify Navigate To Resource Management PageVerify Navigate To Resource Management Page [Documentation] Login to GUI and perform page navigation to ... Resource Management page and verify it loads successfully. [Tags] Verify_Navigate_To_Resource_Management_Page Page Should Contain Element ${xpath_resource_management_header}测试目的验证能够导航到 Resource Management 页面并且页面加载成功。实际步骤由于Suite Setup已经完成登录并导航到 Resource Management → Power 页面所以该用例只检查页面标题元素是否存在${xpath_resource_management_header} //h1[contains(normalize-space(.), Power)]也就是说它验证的是页面 H1 标题中是否包含Power。验证点Power 页面标题存在。间接说明导航成功。用例 2Verify Able To Set Power Cap ValueVerify Able To Set Power Cap Value [Documentation] Verify that the power cap value can be set successfully. [Tags] Verify_Able_To_Set_Power_Cap_Value Page Should Contain Element ${xpath_power_tab_power_consumption} Page Should Contain Element ${xpath_power_cap_setting} Page Should Contain Element ${xpath_power_cap_apply} Page Should Contain Checkbox ${xpath_power_cap_checkbox} Click Element ${xpath_power_cap_checkbox} ${value} Evaluate random.randint(1, 10000) modulesrandom Input Text ${xpath_power_cap_value} ${value} Page Should Contain Element ${xpath_asset_tag_save_button} Click Element ${xpath_asset_tag_save_button}测试目的验证 Power Cap 值是否可以设置成功。执行步骤检查页面存在Current power consumptionPower cap settingApply power cap检查 Power Cap 复选框存在。点击复选框启用 Power Cap 设置。随机生成一个 1 到 10000 之间的整数${value} Evaluate random.randint(1, 10000) modulesrandom将随机值输入到 Power Cap 输入框Input Text ${xpath_power_cap_value} ${value}检查 Save 按钮存在。点击 Save 按钮保存。验证点目前只验证了元素存在、输入框可输入、Save 按钮可点击。关键问题代码中已经注明# Need to add verification step to check if the power cap value is set successfully. # once the open issue is resolved, add verification step here.也就是说该用例目前没有形成闭环验证。点击 Save 后并没有验证是否出现保存成功提示Power Cap 值是否回显正确刷新页面后值是否仍然存在后端 Redfish/API 是否真正生效。因此该用例目前只能算“操作执行型”测试不能算完整的“功能验证型”测试。三、执行流程总结整个套件的执行顺序是Suite Setup Execution启动浏览器并登录 GUI导航到 Resource Management → Power 页面。执行测试用例 1验证 Power 页面标题存在。执行测试用例 2检查 Power Cap 相关元素启用 Power Cap输入随机值点击 Save。Suite Teardown关闭浏览器。四、主要问题与改进建议保存后缺少验证应增加保存成功提示、值回读、刷新后校验或 API 校验。随机值范围可能不符合实际规格1~10000只是随机范围不一定符合 BMC 的 Power Cap 允许范围。可以根据实际情况进行调整变量命名不一致${xpath_asset_tag_save_button}实际是 Power Cap 的 Save 按钮建议改名为${xpath_power_cap_save_button}。不适用文本查找而是power-button-savePowerCapValue总体来看这个测试套件完成了登录、导航、Power Cap 设置操作的基础流程但第二个核心用例还缺少保存结果验证属于待完善的半闭环测试。
返回列表