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.

基于51单片机,实现对直流电机的调速、测速以及正反转控制。项目包含完整的仿真文件、源程序、原理图和PCB设计文件,适合学习和实践51单片机在电机控制方面的应用。 功能特点 调速控制:通过按键调整PWM占空比,实现电机的速度调节。 测速功能:采用霍尔传感器非接触式测速,实时显示电机转速。 正反转控制:通过按键切换电机的正转和反转状态。 LCD显示:使用LCD1602液晶显示屏,显示当前的转速和PWM占空比。 硬件组成 主控制器:STC89C51/52单片机(与AT89S51/52、AT89C51/52通用)。 测速传感器:霍尔传感器,用于非接触式测速。 显示模块:LCD1602液晶显示屏,显示转速和占空比。 电机驱动:采用双H桥电路,控制电机的正反转和调速。 软件设计 编程语言:C语言。 开发环境:Keil uVision。 仿真工具:Proteus。 使用说明 液晶屏显示: 第一行显示电机转速(单位:转/分)。 第二行显示PWM占空比(0~100%)。 按键功能: 1键:加速键,短按占空比加1,长按连续加。 2键:减速键,短按占空比减1,长按连续减。 3键:反转切换键,按下后电机反转。 4键:正转切换键,按下后电机正转。 5键:开始暂停键,按一下开始,再按一下暂停。 注意事项 磁铁和霍尔元件的距离应保持在2mm左右,过近可能会在电机转动时碰到霍尔元件,过远则可能导致霍尔元件无法检测到磁铁。 资源文件 仿真文件:Proteus仿真文件,用于模拟电机控制系统的运行。 源程序:Keil uVision项目文件,包含完整的C语言源代码。 原理图:电路设计原理图,详细展示了各模块的连接方式。 PCB设计:PCB布局文件,可用于实际电路板的制作。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值