Test Essay

Test Essay------Alpha Testing

Introduction & Background:

In this section, we need to do the testing for our completed functions of our software. In this period of alpha sprint, functions include registration, login, and chat-with-friends is considered to be tested in this part.

In this section, some methods of software function testing are conducted to check whether the functions can be implemented correctly. In the coding part, the programmers do the white-box testing for the unit test. Since in this alpha sprint only some independent functions are completed, so the functions testing will be mainly considered.

In this testing part, we use Zen Taoism to do the project management, which can help us to upload the defects and manage the exist defects. Besides, we also implemented our auto-test using selenium. Also, we use Excel to write the user cases and implement the defect management.

In this whole testing process, we implemented the software testing followed the below steps:

1. Requirement Review
2. Plan Writing
3. Test Case Design
4. Test Case Execution
5. Defect Management
6. Test Report

With these six steps, these functions which are required to be tested will be conducted.


Requirement Review

In these alpha sprints, we basically implemented the functions of registration, login and chat-with-friends function. These functions have been already completed. Through the testing in the Unity engine, these functions are verified to pass.

Plan Writing

In this section, we set up the strategies of how we test these two parts.
First is the division of the work.

1. The unit code testing(White Box Testing) are conducted by the programmers:Wang Zhengxian, Chen Kun, Yu Yuxing
2. The Black Box Testing are conducted by the testing personnel: Yuan Chengrui
3. User Case Design, Execution and Reporting: Yuan Chengrui.

Second is the process of this alpha testing:

1. The programmers do the unit testing to guarantee the source code has no bugs.
2. The programmers send the source code of the project to testing personnel.
3. The testing personnel should completed the user case design ahead of time and conducted the user case excecution
4. Finding error and doing the defect management
5. Regression testing

The flow chart of the procedure is shown as follows:

在这里插入图片描述

Test Case Design

We design the user cases separately corresponding to our functions:
In this part, we use Excel to do the user cases design and management. And we use equivalence class partitioning and boundary value testing in this part to generate these three test cases.

The GitHub Responsory are here: Click here to get the test case file

Test Case1: Registration
在这里插入图片描述

Test Case2: Login
在这里插入图片描述

Test Case3: Chat

在这里插入图片描述

After designing these cases, we can implement the executions and then find the errors existing in the project.

Defect Management

In this part, we need to handle the defects we tested in the project, and we found some bugs. By the way, we cannot avoid every defect in an entire project. The efforts we made is to try our best to let the bugs as less as possible.
The existing section of our project is not that complicated, and we only found 2 bugs and they have been already fixed. (Regression test has been conducted)
在这里插入图片描述

在这里插入图片描述

Test Experience & Comments

In this period of test, we commanded the basic skills of the software testing and had a better understanding of the importance of software testing. In this test, we experienced the whole process of the software test and completed the function test. Although some functions have been tested, we cannot completely avoid getting bugs in this project, which urges us to do more tests and consider more conditions and requirements we may be confronted in the next stage.

In the next period, we are about to do more test like interface test, systematically test and acceptance test etc. And in order to make our software better, we will definitely do more tests in the next stage, which can find more bugs or some error we are not expected for.


Summary

In this section, we implemented the testing procedure for our finished functions. Basically, we test the registration, login and chat-with-friends parts in our software. We design the test cases and do the execution with this test cases. Finally, we find the defects in these functions and doing the defect management so that our functions can be implemented correctly.

基于遗传算法的新的异构分布式系统任务调度算法研究(Matlab代码实现)内容概要:本文档围绕基于遗传算法的异构分布式系统任务调度算法展开研究,重点介绍了一种结合遗传算法的新颖优化方法,并通过Matlab代码实现验证其在复杂调度问题中的有效性。文中还涵盖了多种智能优化算法在生产调度、经济调度、车间调度、无人机路径规划、微电网优化等领域的应用案例,展示了从理论建模到仿真实现的完整流程。此外,文档系统梳理了智能优化、机器学习、路径规划、电力系统管理等多个科研方向的技术体系与实际应用场景,强调“借力”工具与创新思维在科研中的重要性。; 适合人群:具备一定Matlab编程基础,从事智能优化、自动化、电力系统、控制工程等相关领域研究的研究生及科研人员,尤其适合正在开展调度优化、路径规划或算法改进类课题的研究者; 使用场景及目标:①学习遗传算法及其他智能优化算法(如粒子群、蜣螂优化、NSGA等)在任务调度中的设计与实现;②掌握Matlab/Simulink在科研仿真中的综合应用;③获取多领域(如微电网、无人机、车间调度)的算法复现与创新思路; 阅读建议:建议按目录顺序系统浏览,重点关注算法原理与代码实现的对应关系,结合提供的网盘资源下载完整代码进行调试与复现,同时注重从已有案例中提炼可迁移的科研方法与创新路径。
【微电网】【创新点】基于非支配排序的蜣螂优化算法NSDBO求解微电网多目标优化调度研究(Matlab代码实现)内容概要:本文提出了一种基于非支配排序的蜣螂优化算法(NSDBO),用于求解微电网多目标优化调度问题。该方法结合非支配排序机制,提升了传统蜣螂优化算法在处理多目标问题时的收敛性和分布性,有效解决了微电网调度中经济成本、碳排放、能源利用率等多个相互冲突目标的优化难题。研究构建了包含风、光、储能等多种分布式能源的微电网模型,并通过Matlab代码实现算法仿真,验证了NSDBO在寻找帕累托最优解集方面的优越性能,相较于其他多目标优化算法表现出更强的搜索能力和稳定性。; 适合人群:具备一定电力系统或优化算法基础,从事新能源、微电网、智能优化等相关领域研究的研究生、科研人员及工程技术人员。; 使用场景及目标:①应用于微电网能量管理系统的多目标优化调度设计;②作为新型智能优化算法的研究与改进基础,用于解决复杂的多目标工程优化问题;③帮助理解非支配排序机制在进化算法中的集成方法及其在实际系统中的仿真实现。; 阅读建议:建议读者结合Matlab代码深入理解算法实现细节,重点关注非支配排序、拥挤度计算和蜣螂行为模拟的结合方式,并可通过替换目标函数或系统参数进行扩展实验,以掌握算法的适应性与调参技巧。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值