[Kde-hardware-devel] Testing backends

[Michael Zanetti]

On Tuesday 27 July 2010 17:31:49 Kevin Ottens wrote:
> On Monday 26 July 2010 22:24:42 Michael Zanetti wrote:
> > what is the best way
> > to test solid backends?
> 
> If we're talking about unit tests, there's no good
> way of doing it unfortunately since you'd need to simulate the subsystem
> you query... Not easy to have something reusable across backends.
> 
> > I have
> > reached a point where solid-hardware isn't enough any more for
> > testing my implementations. For example it seems there is now way to test 
> > functions like DeviceManager::deviceFromQuery()
> 
> "solid-hardware query 'predicate'
> ['parentUdi']" isn't good enough for you?

It is... I just have missed the 'predicate' option...

> For a full list of supported
> commands: solid-hardware --commands
> 

Yeah, I know the --commands switch. But I still couldn't find everything I 
needed like the two beforementioned examples.

> > or Device::description() using solid-
> 
> hardware.
> 
> This feature was actually missing from solid-hardware until
> r1155547 that I just committed in trunk.
> 

Great!

> > Is there another tool I'm not
> 
> aware of for deeper interaction with a
> 
> > backend?
> 
> Nope. For the events
> though (deviceAdded/deviceRemoved), solid-hardware is not practical, so
> using branches/work/~ervin/solidhardwarebrowser would help. Note that
> solidhardwarebrowser would need a lifting though.
> 

Ok, that helps, solid-hardware is of course good enough for me. There were 
just a few features that I eiter missed or haven't been there till now. I will 
check out the solidhardwarebrowser and see if I can use it.

Thanks,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-hardware-devel/attachments/20100729/42dc05dc/attachment.sig