Last modified by gjo on 2023/09/11 16:17
<
From version < 2.1 >
edited by gjo
on 2013/07/04 12:55
To version < 3.1 >
edited by gjo
on 2013/07/04 14:23
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,1 +1,150 @@
1 -coming soon...
1 +To verifiy the continous work will be correct a Junit regressiontest was implemented.
2 +
3 +In these test a model (SCL) and the corresponding ESO file is needed. The test will generate a VHDL component from the model and a testbench from the ESO file and test them against each other. This will be done for all models that are stored in the models repository (if it is complete programmed ).
4 +
5 +== What is needed ==
6 +
7 +----
8 +
9 +The main thing that is needed is the ISE Suite. It contains a compiler to compile the SCL-VHDL file and a simulator (ISIM) to test the SCL-VHDL-Model.
10 +
11 +A very big advantage is that the ISE compiler and simulator can be controlled by a shell command. As we want to control and start this test with eclipse, this interface will be used. So Eclipse is additional needed. The whole test is a JUnit test.
12 +
13 +== Result ==
14 +
15 +----
16 +
17 +This JUnit test, test all models in the appopriate repository. For every test a JUnit error trace will be generated. By this way it is traceable which models testing fails or work.
18 +
19 +Example: JUnit failure trace. Two models were tested //test.scl// and //test1.scl//
20 +
21 +|=(((
22 +JUnit Test Without Failure (test.scl)
23 +)))
24 +|(((
25 +[[image:attach:junit.PNG]]
26 +)))
27 +|=(% colspan="1" %)(% colspan="1" %)
28 +(((
29 +JUnit Test With Failure (test1.scl)
30 +)))
31 +|(% colspan="1" %)(% colspan="1" %)
32 +(((
33 +[[image:attach:junit_fail.PNG]]
34 +)))
35 +
36 +A very good thing is that the JUnit error trace contains the missed assertions. So it is exactly traceable where the failure raises.
37 +
38 +== Technical View ==
39 +
40 +----
41 +
42 +Now a little more technical
43 +
44 +=== ISE Compiler ===
45 +
46 +The ISE compiler is accessable through a shell command. To get the compiler work, we must give the compiler a set of parameters.
47 +
48 +A compiler command look like this:
49 +
50 +{{code}}
51 +fuse -intstyle ise -incremental -o tb_test_isim_beh -prj test.prj
52 +
53 +fuse: the ISE compiler
54 +instyle: compile message level
55 +incremental: build files incremental
56 +o: object file (runnable exe)
57 +prj: project file
58 +{{/code}}
59 +
60 +The object file is the executeable file which is needed for simulation.
61 +
62 +The project file (prj) contains all vhdl that are nedded for the current compile process. In our test case these are all file that describe the model and the testbench file.
63 +
64 +=== ISE Compiler ===
65 +
66 +The ISE simulator is accessable through a shell command. To get the simulator work, we must give the simulator a set of parameters.
67 +
68 +A simulation command look like this:
69 +
70 +{{code}}
71 +tb_test_isim_beh.exe -intstyle ise -tclbatch tes.cmd -log out.log -sdfnowarn
72 +
73 +instyle: compile message level
74 +tclbatch: a file which contains simulation information
75 +log: specifies the log file
76 +sdfnowarn: supress warnings
77 +{{/code}}
78 +
79 +=== prj File ===
80 +
81 +The project file contain all relevant vhd file which are needed for a succesfull compile. In this case the testbench file is also included becuase it should be tested afterwards.
82 +
83 +Here an example of the project file is shown.
84 +
85 +{{code}}
86 +vhdl work "abo.vhd"
87 +vhdl work "abo_tb.vhd"
88 +{{/code}}
89 +
90 +The abo.vhd corresponds to the SCL model and contians the component that behaves like the model. abo_tb.vhd is the generated testbench from core ESO file.
91 +
92 +=== cmd File ===
93 +
94 +The command file contains simulation information. In these case we need only the time the simulaion must take.
95 +
96 +Here an example of an command file:
97 +
98 +{{code}}
99 +run 1000 ns;
100 +quit
101 +{{/code}}
102 +
103 +=== batch file ===
104 +
105 +To run everything automatically a batch file a generate which executes the compiling and simulation process.
106 +
107 +Here an example of such a batch file:
108 +
109 +{{code}}
110 +ise_path="/C/Xilinx/14.5/ISE_DS/ISE/"
111 +project="test.prj"
112 +toplevelEntity="test_tb"
113 +simulation_tcl="test.cmd"
114 +
115 +export PLATFORM=nt
116 +export XILINX=$ise_path
117 +export PATH=$PATH:$XILINX/bin/$PLATFORM
118 +export LD_LIBRARY_PATH=$XILINX/lib/$PLATFORM
119 +
120 +binary="tb_test_isim_beh"
121 +compile_params="-intstyle ise -incremental -o "$binary" -prj "$project
122 +sim_params="-intstyle ise -tclbatch "$simulation_tcl" -log out.log -sdfnowarn"
123 +tmp_out="sim_out.txt"
124 +
125 +fuse $compile_params $toplevelEntity
126 +"./"$binary".exe" $sim_params
127 +echo -e out.log | cat out.log | grep 'Error:' | sed 's/at.*ps: //' >> $tmp_out
128 +{{/code}}
129 +
130 +This file would not be explained in detail. In the first block the needed file are assigned. In the second the ISE Path is set. In the fourth part the compile and simulation params are set and in the last part the compilation and simulation is executed.
131 +
132 +Some small hints:
133 +
134 +* toplevelEntiy specifies the toplevel entity which should be used, in our case the testbench entity.
135 +* sim_out.txt is the log file which will be used later to fill failure information into the JUnit failure trace.
136 +* last line: this line takes the simulation log and performs a string operation which pipes only the errors to the sim_out.txt
137 +
138 +=== The proper Test ===
139 +
140 +And how does the simulation works? Here is a little controllflow diagram which expresses what will be done which each model that will be tested.
141 +
142 +
143 +
144 +
145 +
146 +
147 +
148 +
149 +
150 +
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -7111272
1 +7111274
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7111272/Regressiontest - Automated Testing
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7111274/Regressiontest - Automated Testing

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage