From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 3/3] android/tester: Add test Connect returns valid fd
Date: Fri, 20 Dec 2013 14:09:53 +0200 [thread overview]
Message-ID: <1387541393-2669-3-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1387541393-2669-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
The case is analog for similar test case with listen().
---
android/android-tester.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/android/android-tester.c b/android/android-tester.c
index 4148c0e..fa65416 100644
--- a/android/android-tester.c
+++ b/android/android-tester.c
@@ -1101,12 +1101,14 @@ static const struct socket_data btsock_inv_params_chan_uuid = {
};
static const struct socket_data btsock_success = {
+ .bdaddr = &bdaddr_dummy,
.sock_type = BTSOCK_RFCOMM,
.channel = 1,
.service_uuid = NULL,
.service_name = "Test service",
.flags = 0,
.expected_status = BT_STATUS_SUCCESS,
+ .test_channel = false
};
static const struct socket_data btsock_success_check_chan = {
@@ -1619,6 +1621,10 @@ int main(int argc, char *argv[])
&btsock_inv_listen_listen,
setup_socket_interface, test_listen_listen, teardown);
+ test_bredrle("Socket Connect - Check returned fd valid",
+ &btsock_success, setup_socket_interface,
+ test_generic_connect, teardown);
+
test_bredrle("Socket Connect - Invalid: sock_type 0",
&btsock_inv_param_socktype, setup_socket_interface,
test_generic_connect, teardown);
--
1.8.3.2
next prev parent reply other threads:[~2013-12-20 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 12:09 [PATCH 1/3] android/tester: Add Socket test invalid double listen Andrei Emeltchenko
2013-12-20 12:09 ` [PATCH 2/3] android/tester: Make code consistent using < 0 comparison Andrei Emeltchenko
2013-12-20 12:09 ` Andrei Emeltchenko [this message]
2013-12-20 12:23 ` [PATCH 1/3] android/tester: Add Socket test invalid double listen Johan Hedberg
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=1387541393-2669-3-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.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