Linux bluetooth development
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: linux-bluetooth@vger.kernel.org
Subject: working bluetooth obex test scripts?
Date: Thu, 9 Jun 2016 16:39:13 -0400	[thread overview]
Message-ID: <20160609203913.GI90326@redhat.com> (raw)

Hi,

I was trying to put together some bluetooth obex test scripts to help
continuously verify that interface works reliably on various machines we
have.

However, I am not very successful with the stuff in the test/ directory.

I started by focusing on ftp-client -d <address> -l.  I assume I had to run
the 'simple-obex-agent' on the machine with <address>.

Working around the dbus.SessionBus errors (I am connecting through ssh
instead of the desktop), I get 'Unable to find service record' after
ftp-client creates a session.

I think that is because it isn't connecting the remote agent correctly?

Anyway, pointers for good scripts to run to test the obex interface?

Cheers,
Don


             reply	other threads:[~2016-06-09 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 20:39 Don Zickus [this message]
2016-06-09 20:50 ` working bluetooth obex test scripts? Barry Byford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160609203913.GI90326@redhat.com \
    --to=dzickus@redhat.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox