[JBoss jBPM] - Re: fork and join childeren
by tbeernot
Ok.
Now, I fully appriciate the help you guys are giving me. Again many thanks for that. And I even appriciate the promotion of unittests, although you are talking to an already converted believer. But I do think it is a bit overdone to try to tell me how I should work my way to a unittest, as long as -when I'm done- there is a nice unittest with assertions.
So when I'm busy learning something (like JBPM here) I prefer prints. Simple, straight forward and it outputs the info exactly at the right time, over and over again, without me having to think in advance about what should be there. Token classes? Node classes? Iterator? I'm learning what should be there, prints are telling me this, and then I can replace the prints with assert and continue to the next part. Step by step.
I most definitely use debuggers, but for when I need to trace the execution, and they often involve tiredsome manual "step-in", "execute-out", "run-to" and other program flow management, which I do not like. Especially if certain pieces of code have to be navigated multiple times. Plus, how do you think I should have illustrated my problem we discussed in the thread? Make a movieclip of the debugger screen?
So, again, I'm very grateful for the help, and I'm a great proponent for unittests, but let's keep the how-to-get-there to each's personal taste. I use intermediate prints, you guys use asserts. Great. At least we all write unittests.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189400#4189400
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189400
17 years, 4 months
[JBoss jBPM] - Re: fork and join childeren
by kukeltje
anonymous wrote : if you wanna really see the values variables and tokens you must debug...
+1
anonymous wrote : so... try to leave println...
leave as in abandon/ditch/get rid of... I guess...
anonymous wrote : I do not understand the problem. In order to assert something I first need to check if my idea of what is suppose to happen is correct.
That is what you do with an assert.... It prints values as well if they do not match... So you can see what you get is what you expect.
anonymous wrote : There will be no others that ever see the println statements, [/quote
|
| We did and you had to write lots of text explaning what you expected and there were (natural) language barriers.
|
| Personally I do not investigate these kinds of problem reports anymore since it takes WAY to much time, but I respect Mauricio for still doing it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189385#4189385
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189385
17 years, 4 months