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

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 -To verifiy the continous work will be correct a Junit regressiontest was implemented.
1 +To verify the continous work will be correct, a Junit regressiontest was implemented.
2 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 ).
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 completely programmed ).
4 4  
5 5  == What is needed ==
6 6  
... ... @@ -33,7 +33,7 @@
33 33  [[image:attach:junit_fail.PNG]]
34 34  )))
35 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.
36 +A very good thing is that the JUnit error trace contains the missed assertions. So it is exactly traceable where the failure appeared.
37 37  
38 38  == Technical View ==
39 39  
... ... @@ -43,9 +43,9 @@
43 43  
44 44  === ISE Compiler ===
45 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.
46 +The ISE compiler is accessable through a shell command. To get the compiler to work, we must give the compiler a set of parameters.
47 47  
48 -A compiler command look like this:
48 +A compiler command looks like this:
49 49  
50 50  {{code}}
51 51  fuse -intstyle ise -incremental -o tb_test_isim_beh -prj test.prj
... ... @@ -57,15 +57,15 @@
57 57  prj: project file
58 58  {{/code}}
59 59  
60 -The object file is the executeable file which is needed for simulation.
60 +The object file is an executeable file which is needed for simulation.
61 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.
62 +The project file (prj) contains all vhdl that are needed for the current compile process. In our test case these are all file that describe the model and the testbench file.
63 63  
64 64  === ISE Compiler ===
65 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.
66 +The ISE simulator is accessable through a shell command. To get the simulator to work, we must give the simulator a set of parameters.
67 67  
68 -A simulation command look like this:
68 +A simulation command looks like this:
69 69  
70 70  {{code}}
71 71  tb_test_isim_beh.exe -intstyle ise -tclbatch tes.cmd -log out.log -sdfnowarn
... ... @@ -78,7 +78,7 @@
78 78  
79 79  === prj File ===
80 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.
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 because it should be tested afterwards.
82 82  
83 83  Here an example of the project file is shown.
84 84  
... ... @@ -87,13 +87,13 @@
87 87  vhdl work "abo_tb.vhd"
88 88  {{/code}}
89 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.
90 +The abo.vhd corresponds to the SCL model and contains the component that behaves like the model. abo_tb.vhd is the generated testbench from core ESO file.
91 91  
92 92  === cmd File ===
93 93  
94 -The command file contains simulation information. In these case we need only the time the simulaion must take.
94 +The command file contains simulation information. In this case we only need the time that the simulation must take.
95 95  
96 -Here an example of an command file:
96 +Here an example of a command file:
97 97  
98 98  {{code}}
99 99  run 1000 ns;
... ... @@ -102,7 +102,7 @@
102 102  
103 103  === batch file ===
104 104  
105 -To run everything automatically a batch file a generate which executes the compiling and simulation process.
105 +To run everything automatically, a batch file was generated, which executes the compiling and simulation process.
106 106  
107 107  Here an example of such a batch file:
108 108  
... ... @@ -127,20 +127,24 @@
127 127  echo -e out.log | cat out.log | grep 'Error:' | sed 's/at.*ps: //' >> $tmp_out
128 128  {{/code}}
129 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.
130 +This file would not be explained in detail. In the first block the needed files will be assigned. In the second block the ISE Path will be set. In the third part the compile and simulation parameter are set and in the last part the compilation and simulation is executed.
131 131  
132 132  Some small hints:
133 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
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 file and performs a string operation which that pipes only the errors to the sim_out.txt
137 137  
138 138  === The proper Test ===
139 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.
140 +And how does the simulation works? Here is a little control flow diagram which expresses what will be done with each model that will be tested.
141 141  
142 -
142 +[[image:attach:junit_workflow.PNG]]
143 143  
144 +Some additional detailed information:
145 +
146 +For every model which should be tested, a folder with its model name is created. The generated files will be saved to this folder. These folders won't be deleted after the test, they will be deleted befor a new test take place. So it is possible to look at these folders for more information if there are any errors.
147 +
144 144  
145 145  
146 146  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -7111274
1 +8651010
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/7111274/Regressiontest - Automated Testing
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651010/Regressiontest - Automated Testing

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage