Assignment First

英国金士顿大学论文代写:集成测试
1)大爆炸方法
在大爆炸中,所有模块都被测试为一个内聚单元。其优点是不需要单元测试,和多个测试用例,缺点是会有需要生成多个存根和驱动程序。故障隔离也不容易。
考虑情况的情况下,代码1基本上是一个提示用户输入一些细节,代码2是将做一些修改的数据,并把它传递到另一个功能,说代码或方法3将数据保存到一个文件文件。当进行大爆炸测试时,所有三个函数都会立即进行测试。在这里,如果发生故障,人们会很难找到它是否是代码2或3,失败。
2)增量方法
自上而下的方法
在自顶向下的方法,骨骼框架将首先进行测试,然后子功能。让我们考虑上面定义的代码1、2和3作为子函数,然后有一个main函数,它基本上只对文档有访问权限,但不修改、更新或删除它。然后,主要功能是为1,2和3株进行测试,然后将测试1,2和3。在自上而下的方法一个基本的工作程序可以提交给用户,这是一个优势
自下而上的方法
自底向上的方法将开始与1,2和3的测试,然后将测试的主要功能。在底部是一个基本的工作程序的时间将延迟的缺点。
三明治方法-自上而下和自下而上的组合
三明治测试将使用自下而上和自上而下的测试。存根将主要代码创建,他们将被测试,平行的子码1,2和3的测试。优点是代码测试时间大大减少。

英国金士顿大学论文代写:集成测试

1) Big Bang Approach
In the Big bang all modules are tested as a cohesive unit. The advantages are that there is no need for unit testing, and multiple test cases, the disadvantages are that there will be the need to generate multiple stubs and drivers. Fault isolation also will not be easy.
Consider the case scenario where code 1 is basically a prompt to the user to enter some details, code 2 is the will do some modification of the data and pass it onto another function, say code or method 3 will save the data to a document file. When big bang testing is done, all three functions are tested at once. Here if a fault was to occur, one would have a hard time finding whether it was code 2 or 3 that failed.
2) Incremental Approach
a)Top Down Approach
In the top down approach, the skeletal framework will first be tested and then the sub functions. Let us consider code 1, 2 and 3 defined above as the sub functions, and then there is a main function which is basically to just have access to the document, but not modify, update or delete it. Then the main function would be tested with stubs for 1,2 and 3, and then 1,2 and 3 will be tested. In the top down approach a basic working program could be presented to the users and this is an advantage
b)Bottom Up Approach
A bottom up approach will start with the testing of 1,2 and 3 and then the main function will be tested. The disadvantages in the bottom up is that the time for a badic working program would be delayed.

c) Sandwich Approach – Combination of Top Down and Bottom Up
A sandwich testing will use both bottom up and top down testing. The stubs will be created for main code and they will be tested, parallel to the testing of the sub codes 1,2 and 3. Advantage is that the code testing time is reduced considerably.