The process of testing

  Yesterday,I talked about some aspects of testing.That is what we need before develop our testing work.After knowing every detail of requirement,we can begin our work.In the whole course,said simply,it should including design test spec,review them with developer and requirement analysisor,execute them-that is testing course,report issue,test those issues,test new function,write test report ,evaluate the quality of project,and forecast the current of our project.Meanwhile,it also include the output of testing process,like test report.

  We should have a smooth process and a strict regulation.Obviously,every circle in process should link up closly.Every step should be executed orderly.Take an example,we should test elementary function firstly.Or it is not worth testing other function,like integration testing.It is undoubtly waste our time.As well known,different testing has their character.We need according them to develop our work.Another good instance is we should confirm requirement,then begin write our test spec.This represent that there is a causality relation in our prcess.So,base on these two instances,we should consider the relationship between each circle and institute reasonable and coherent test plan.After having plan,everybody in team should establish strict regulation to execute every step in our process.For example,for checking in test result to database,tester may feel that is trouble thing,it would bother their time to fill after run each ticket.They always fill result before leave office.But this would be result in burden of database,and,as manager,they wonder seeing the result of current version of our project.If we check in result as soon as possible,it also lead to decreasing our efficiency.So,this is a contradiction.As a tester manager,need regulate fair and reasonable rule.I think we can use different model,like test case model,result model or something like that,to limit different thinking.Certainly,this model root in wise from whole team.Manager or the person who make model can not set down by himself.It should be discussed and ask suggestion by everybody in team.In this way,this model take on feasibility.Although,there may possess defect and need to be modified,I think that would not effect too much thing.This would advantageous for our prepare work.

  Ok,in the future,I'll disscus on every model in testing,like test spec,test task,and test result. 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
操作系统代码实现:Number Project Name Content Summary State Type 一、Process Scheduling Algorithm Simulation 1、 Simulate the operation of the round-robin algorithm for process scheduling. 2、 Create at least 15 processes and output their scheduling situation under the scheduling algorithm mentioned above and output it to theterminal to check the execution of the algorithm. 3、 The output should include the arrival time of the processes, the end time, and the average execution time. Essential. General 二、Readers-Writer Problem Implmentation 1、 A data set is shared among several concurrent processes: Readers – only read the data set; they do not perform any updates. Writers – can both read and write. 2、 Problem – allow multiple readers (at most 8) to read at the same time. Only one single writer can access the shared data at the same time. Essential. General 三、Program for Least Recently used Algorithm 1、 Create a page access sequence (page number range 0-18) using a random function. The sequence length is 54 and assume that the number of main memory frames allocated to the thread is 6, that is, M = 6. 2、 Implement the LRU algorithm for page replacement on the above access sequence. 3、 Output the page replacement sequence and the page fault rate. Essential. General Requirements 1、 For each experiment project, submit a design report and code. The code should be implemented in C++. The requirements are as follows: a) The content of the design report should include the design ideas and implementation. b) The results of the design report should include testing and running results (screenshots of screen outputs). c) The conclusion of the design report should summarize the problems encountered, the solutions and experiences during the implementation process.
最新发布
06-08

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值