13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with Megatest. If not, see <http://www.gnu.org/licenses/>.
Debugging
---------
A word on Bisecting
~~~~~~~~~~~~~~~~~~~
Bisecting is a debug strategy intended to speed up finding the root
cause.
|
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
|
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with Megatest. If not, see <http://www.gnu.org/licenses/>.
Debugging
---------
Well Written Tests
~~~~~~~~~~~~~~~~~~
Test Design and Surfacing
^^^^^^^^^^^^^^^^^^^^^^^^^
Design your tests to surface errors. Ensure that all logs are processed by logpro and can be reached by a mouse click or two from the test control panel.
using the tool to make life easier
layers - less is often more
Clicks-to-error
A word on Bisecting
~~~~~~~~~~~~~~~~~~~
Bisecting is a debug strategy intended to speed up finding the root
cause.
|
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
step" to only rerun the step or click on "restart from here" to rerun
that step and downstream steps.
NOTE 1: visual feedback can take some time, give it a few seconds and
you will see the step change color to blue as it starts running.
NOTE 2: steping through only works if you are using ezsteps.
Config File Processing
^^^^^^^^^^^^^^^^^^^^^^
As described above it is often helpful to know the content of
variables in various contexts as Megatest works through the actions
needed to run your tests. A handy technique is to force the startup of
|
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
|
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
step" to only rerun the step or click on "restart from here" to rerun
that step and downstream steps.
NOTE 1: visual feedback can take some time, give it a few seconds and
you will see the step change color to blue as it starts running.
NOTE 2: steping through only works if you are using ezsteps.
Bisecting megatest.csh/sh
^^^^^^^^^^^^^^^^^^^^^^^^^
Sometimes finding the environment variable that is causing the problem can be very difficult. Bisection can be applied.
Edit the megatest.csh or megatest.sh file and comment out 50% per round, source in fresh xterm and run the test.
This idea can also be applied to your .cshrc, .bashrc, .aliases and other similar files.
csh and -f
^^^^^^^^^^
A common issue when tcsh or csh shells are used for scripting is to forget or choose to not use -f in your #! line
.
Config File Processing
^^^^^^^^^^^^^^^^^^^^^^
As described above it is often helpful to know the content of
variables in various contexts as Megatest works through the actions
needed to run your tests. A handy technique is to force the startup of
|