Linux bluetooth development
 help / color / mirror / Atom feed
From: Christian Fetzer <christian.fetzer@oss.bmw-carit.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/1] test: Make map script a command line client
Date: Mon, 14 Jan 2013 11:46:58 +0100	[thread overview]
Message-ID: <50F3E222.2060709@oss.bmw-carit.de> (raw)
In-Reply-To: <CABBYNZJJCW0oUOo_7F0VFcZVEFCVHZJpwGndke6P3T2pR9MqBg@mail.gmail.com>

Hi Luiz,

On 01/13/2013 04:29 PM, Luiz Augusto von Dentz wrote:
> I wonder if we should complicate more the testing scripts adding such 
> futures or start working in a proper C tool such as bluetoothctl e.g. 
> obexctl? -- Luiz Augusto von Dentz -- To unsubscribe from this list: 
> send the line "unsubscribe linux-bluetooth" in the body of a message 
> to majordomo@vger.kernel.org More majordomo info at 
> http://vger.kernel.org/majordomo-info.html 

In my opinion it would be nice if the test scripts support most profile 
features that are implemented in bluez/obexd.
That's why I extended the map-client. I tried to keep it as simple as 
possible while focusing also on good testing usability.

The language used for the test scripts / programs doesn't matter that 
much since the scripts are mainly for developers/testers.
Python has some advantages, the scripts can be changed easily while 
working on new features.

However, until some script replacement tool is available, it still would 
make sense to extend/maintain the scripts that are there.

Regards,
Christian

      reply	other threads:[~2013-01-14 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 16:44 [PATCH 1/1] test: Make map script a command line client Christian Fetzer
2013-01-11 20:48 ` Marcel Holtmann
2013-01-13 15:29   ` Luiz Augusto von Dentz
2013-01-14 10:46     ` Christian Fetzer [this message]

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=50F3E222.2060709@oss.bmw-carit.de \
    --to=christian.fetzer@oss.bmw-carit.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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