unit tests failing

Milian Wolff mail at milianw.de
Wed Jul 20 22:59:55 UTC 2011

David Nolden, 20.07.2011:
> Is the UI built up properly (including widgets) in the unit-test?
> I cannot see how it's related to the working-sets, those don't
> manipulate any widget-structures. Any widget that is visible should
> have a parentWidget(). Maybe the timing of the signal is the problem.

Yes, definitely timing is an issue. but here you can see the same bug in a 
full blown kdevelop session:


Look at the attached backtrace of comment #1 (unrelated to the initial 
backtrace, but just the same I'm talking about here)

And yeah, the DocumentControllerTest also initializes the core in 
Core::Default-mode, i.e. with fullblown UI (it's just hidden now).

Again, shows that I really need to spent time on my unit-testable-workingsets 
branch... Hope to finish that on the train on Sunday, lets see.

Anyhow, if noone finds a way to fix this I'll try to give it a shot next week 

Milian Wolff
mail at milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110721/e096e2a9/attachment.sig>

More information about the KDevelop-devel mailing list