testing types

本文概述了针对新旧硬件及软件的各种测试类型,包括接受测试、主动测试、即兴测试等,并详细解释了每种测试的目的与实施方式。
testing types

Following is a summary of the various tests that are performed on new and revised hardware and software. Thai Ann Loe made a major contribution to this definition.

Acceptance Test
The test performed by users of a new or changed system in order to approve the system and go live. See user acceptance test.

Active Test
Introducing test data and analyzing the results. Contrast with "passive test" (below).

Ad Hoc Test
Informal testing without a test case.

Age Test (aging)
Evaluating a system's ability to perform in the future. To perform these tests, hardware and/or test data is modified to a future date.

Alpha Test
The first testing of a product in the lab. Then comes beta testing. See alpha test.

Automated Test
Using software to test software. Automated tests may still require human intervention to monitor stages for analysis or errors.

Beta Test
Testing by end users. Follows alpha testing. See beta test.

Black Box Test
Testing software based on output only without any knowledge of internal operation. Contrast with "white box test."

Dirty Test
Same as "negative test."

Environment Test
A test of new software that determines whether all transactions flow properly between input, output and storage devices. See environment test.

Functional Test
Testing functional requirements of software, such as menus and key commands. See functional test.

Negative Test
Using invalid input to test a program's error handling.

Passive Test
Monitoring the results of a running system without introducing any special test data. Contrast with "active test" (above).

Recovery Test
Testing a system's ability to recover from a hardware or software failure.

Regression Test
To test revised software to see if previously working functions were impacted. See regression testing.

Smoke Test
Turn it on and see what happens. See smoke test.

System Test
Overall testing in the lab and in the user environment. See alpha test and beta test.

Test Case
A set of test data, test programs and expected results. See test case.

Test Scenario
A set of test cases. See test scenario.

Test Suite
A collection of test cases and/or test scenarios. See test suite.

Unit Test
A test of one component of the system. Contrast with "system test."

User Acceptance Test (UAT)
See "acceptance test" above.

White Box Test
Testing software with knowledge of the internal operation. Contrast with "black box test." 
 
多源动态最优潮流的分布鲁棒优化方法(IEEE118节点)(Matlab代码实现)内容概要:本文介绍了基于Matlab代码实现的多源动态最优潮流的分布鲁棒优化方法,适用于IEEE118节点电力系统。该方法结合两阶段鲁棒模型与确定性模型,旨在应对电力系统中多源输入(如可再生能源)的不确定性,提升系统运行的安全性与经济性。文中详细阐述了分布鲁棒优化的建模思路,包括不确定性集合的构建、目标函数的设计以及约束条件的处理,并通过Matlab编程实现算法求解,提供了完整的仿真流程与结果分析。此外,文档还列举了大量相关电力系统优化研究案例,涵盖微电网调度、电动汽车集群并网、需求响应、储能配置等多个方向,展示了其在实际工程中的广泛应用价值。; 适合人群:具备一定电力系统基础知识和Matlab编程能力的研究生、科研人员及从事能源系统优化工作的工程师。; 使用场景及目标:①用于研究高比例可再生能源接入背景下电力系统的动态最优潮流问题;②支撑科研工作中对分布鲁棒优化模型的复现与改进;③为电力系统调度、规划及运行决策提供理论支持与仿真工具。; 阅读建议:建议读者结合提供的Matlab代码与IEEE118节点系统参数进行实操演练,深入理解分布鲁棒优化的建模逻辑与求解过程,同时可参考文中提及的其他优化案例拓展研究思路。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值