SEKE 2012 Proceedings - Knowledge Systems Institute

D. An Example for Parallel Test Paths
Fi gure 2 shows the test scene flow graph of software about
automated teller machine (ATM).
in User.CardId 1 error”
2 1
CardId=100 PS=123
PS=123
3
2 2
CardId=100 PS=123 Output=“Passwo
PS123
rd Error, again”
8
… … … … … …
Figure 2 An example of test scene flow graph
It has eight nodes and twelve edges except the start node
and end node. Seven prime paths can be found:
1) [1, 8]
2) [1, 2, 8]
3) [1, 2, 3, 4, 7, 8]
4) [1, 2, 3, 5, 7, 8]
5) [1, 2, 3, 6, 7, 8]
6) [1, 2, 3, 6, 8]
7) [6, 6]
Then we get the set of test paths:
1) [1, 8]
2) [1, 2, 8]
3) [1, 2, 3, 4, 7, 8]
4) [1, 2, 3, 5, 7, 8]
5) [1, 2, 3, 6, 7, 8]
6) [1, 2, 3, 6, 8]
7) [1, 2, 3, 6, 6, 7, 8]
For each test scene, we can design the test cases from
different test equivalence class and set up a symbol to indicate
the next scene as TABLE I showed, which contains SceneId, a
serial number assigned to a test scene; CaseId, a serial number
assigned to a test case; Prerequisites describes the values of
the conditions and environment variable before the test is
performed; TestData are input data; ExpectedResult are
outputs or activities; NextScene indicates the following scene.
Test_Manager store the test case in XML document as Figure
3 and analyze the XML document to generate test scripts.
TABLE I. TEST SCENE AND TEST CASES
SceneId CaseId Prerequisites TestData ExpectedResult NextScene
100 exits in CardId Output=“Input
1 1
2
User.CardId =100 Password”
1 2 101 not exits CardId=10Output= “Card 8
100 exits in User.CardId
CardID=100
Output=“Input Password”
scene2
……
……
……
Figure 3 Test cases in XML
IV. SCHEDULING PARALLEL TEST PATHS AND INTEGRATING
TEST RESULTS
The test paths can be dispatched on AT-Cloud and be
tested in parallel, which related with scheduling test paths and
integrating test results.
A. Schedule Parallel Test Paths
The goal of test task scheduling is to find an assignment
function to dispatch the test tasks for minimizing test time.
This paper considers test path length as dec ision
making criteria.
path-length: the number of nodes between beginning and
end nodes in a test path.
priority: the longer path has higher priority; the front path
near the start point of the graph has higher priority.
G iven a set of test paths set S = {s 1 , s 2 , ..., s m }, there is a set
of VMs M in cloud, M = {m 1 , m 2 , ..., m n } and a set T for fail
test paths. The schedule procedure in AT-Cloud is as follows.
1) Sorting test paths
If S is not empty, then sort the test paths based on path's
priority in descending order.
2) Choose or creating VMs
I f machine set M is empty, which means VMs in AT-Cloud
with the required environment for the test task is not available,
notify the cloud to create a VM for the test task according to
the quantity of test paths and the resource requirements. If M
is not empty, choose a VM that satisfied the test requirement.
3) Dispatch test paths to VMs
281