linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Test coverage for "add advertising" - timeouts, missing tests
@ 2015-05-26  1:14 Florian Grandel
  0 siblings, 0 replies; only message in thread
From: Florian Grandel @ 2015-05-26  1:14 UTC (permalink / raw)
  To: Arman Uguray, Johan Hedberg; +Cc: BlueZ development, Marcel Holtmann

Hi Arman and Johan,

Marcel would like to see a test that covers an advertising instance 
timeout to further reduce the potential for regressions caused by the 
multi-advertising changes.

I may be mistaken but I think we do not have such a test in mgmt-tester, 
yet.

(We do have tests that set a timeout in an add advertising call but the 
timeout will not expire as the delayed work is canceled. This is 
intended behavior - just not the test I would have to write.)

Today, Arman and I quickly discussed the possibility to test timeouts 
and we first thought that the tester would support it. But then I 
couldn't really find a hook to do so.

So now I'm left with a few questions:
- Did I overlook the hook to test timeouts?
- If not: Should we introduce one?
- If so: Is there a way to "simulate" the timeout in a way that doesn't 
require us to actually wait for a second or even more? Otherwise timeout 
tests would considerably slow down test execution.

And somewhat related a different problem that I encountered today:
- Is there a way to test that a given event is NOT being triggered by a 
test case? Maybe there's a way to find out when no more events can be 
expected so that we don't have to wait - which would considerably slow 
down tests again and would not be reliable anyway?

Thanks for your help!

Florian

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-05-26  1:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-26  1:14 Test coverage for "add advertising" - timeouts, missing tests Florian Grandel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).