DCOP and testing

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

DCOP and testing
by Markus Heller on Wednesday 06/Oct/2004, @05:57

Hi,

well, actually my (following) idea applies to all applications, not just KOffice / KWord:

Actually somebody would have to sit down and work on this: If the developers strictly follow the idea that every graphical user element should also be accessible via DCOP, we could automate quality ensurance:

We would only have to set up usage paths through the applications and replay these paths again and again with every compilation stage. Errors would come up automatically and our software quality would be unbeatable. Further more, this would increase the "manageability" of software. Which is a concept that is by far underdeveloped in the Windows world.

Such a replay application - which would be able to monitor application performance from a user perspective - could report these statistics to an snmp agent like ucd-snmpd and enable the setup of automated software performance management stations in the sense of service management.

Especially those highly complex applications like the KOffice series with their high share of graphical stuff will have to consider this...

Markus

Related Links

·   Articles on Interviews
·   Also by Markus Heller
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: DCOP and testing
by Waldo Bastian on Wednesday 06/Oct/2004, @09:16

Great idea! What is stopping you from turning it in reality?

[ Reply To This | View ]

Re: DCOP and testing
by Markus Heller on Wednesday 06/Oct/2004, @09:58

I'm already trying out things in this direction... Especially towards automated Web access through DCOP (remote controlling konqueror).

Unfortunately I don't have that much Qt and kdelibs programming experience, but I'm getting on. I guess I will be further in about half a year. :-)

Markus

[ Reply To This | View ]

Re: DCOP and testing
by David Faure on Wednesday 06/Oct/2004, @14:22

> that every graphical user element should also be accessible via DCOP, we could automate quality ensurance

We can also do that without developing our own tool, simply by using KDExecutor.

http://www.klaralvdalens-datakonsult.se/?page=products&sub=kdexecutor

The tool exists - it's just that nobody took the time to create testcases.
Feel like giving a hand with that? :)

[ Reply To This | View ]

Re: DCOP and testing
by Paul Walker on Thursday 07/Oct/2004, @05:20

The problem with KDExecutor is that it isn't free. Okay, there's a "free beer" version, but not one that people can take apart and put back together, update as they develop KDE/Qt, fix bugs in, and so forth.

Defining test cases now would be useful, I agree, but it should be done with the aim of being able to replay them from a free-free executor. :-)

[ Reply To This | View ]

Re: DCOP and testing
by Datschge on Wednesday 06/Oct/2004, @14:43

As far as I understood Harald's speech at the aKademy the accessibility implementation in the upcoming Qt 4 will give you just that through DBUS, access to all widgets, commands/actions and hints including hierarchy. Should be useful for both alternative interfaces (for accessibility) as well as testing (what you mentioned, but also for let's say computer admins checking if the computer is locked down enough using kiosk).

[ Reply To This | View ]

Re: DCOP and testing
by didi on Thursday 07/Oct/2004, @05:22

Or automatically generate screenshots for documentation in all supported languages

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"He may be a Hotmail user, but the patch works, so who am I to argue?" -- Charles Samuels
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.