Markus Barchfeld wrote:
> Martin Krauskopf wrote:
>> Martin Krauskopf wrote:
>>
>>> TBD: mainly adding ruby-debug.rb....
>>>
>> I've just update Kent's ruby-debug and it seems that Markus was
>> successful with propagating his changes directly there into v 0.8, right
>> Markus? Congratulations! :) So there is no need to make it part of
>> "debug-commons" any more?
>>
> Hi Martin!
>
> Sorry also from my side for not replying to your other request earlier.
> But actually there was not much to comment from my side: it sounds good
> to me and just go for it. I will then move the development of the
> debugger tests to debug-commons, too (I have got to get a rubyforge
> account first).
> Do you have any chance to automate the tests and run them on various
> ruby versions (and on different platforms)?
Yup, this is another task. Currently I'm using fresh Ruby build from
ruby_1_8 branch which is the only which works for me. "ruby 1.8.5
(2006-12-25 patchlevel 12)" - the last official release; doesn't pass
the tests. But now it is much easier to catch the culprit. Just one has
to run "rake" (all tests), or better "./kill_debugger; rake" if you are
on Linux and you will quickly catch the culprit - test_class_variables
fails with Segmentation Fault. Than one can play with it repeatedly in
standard manner.
kill_debugger; cd test; ruby cd_variables_test.rb --name
test_class_variables; cd ..
I did not have time to look at it yet. Hopefully soon.
> I had lot of trouble with
> running the tests as part of the Eclipse JUnit test suite. They took a
> lot of time and were unstable but it should get better without the Java
> stuff around.
Yes, it's currently very quick process to catch and patch the bug. I've
stabilized all active and commented tests so everything passes now. Take
a look at the project I've send you if you want. I'll establish project
soon.
Also there might be some changes which differs from eclipseDebug.rb. I
hope I'll able to provide some merging-patch for RDT as well as I wrote
(it will be small).
> I think we should also run the test suite with ruby-debug if it is
> supposed to be a sort of compatibility test. And I would have to
> maintain the Test Suite in org.rubypeople.rdt.debug.test. otherwise.
> Furthermore there are also some extensions to ruby-debug which should be
> tested, too.
I'm not sure about this. Did not know how much protocol of ruby-debug
differs from classic-debug after your recent changes. But I think that
testbase.rb and reader.rb should be generally useful. Maybe few
tweaks/generalization will be needed. I need to take a look at
ruby-debug soon anyway so I would write/help_with those test. I would
post here before starting to work on them to prevent double-effort.
Regarding org.rubypeople.rdt.debug.test, it should probably be trimmed
to minimum, needed for testing Java-layer(CommandFactories,
DebugProxies, ...), not protocol itself. In the future I would also like
to make the Java-layer part of debug-common project. But there are some
IDE-dependent stuffs as we talked about.... probably off-topic for now.
m.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
