Meego Wiki
Views

Quality/TestSuite/MCTS/Run MCTS/mcts-connman-tests

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Created page with "= mcts-connman-tests = 1. Setup test environement Ethernet network: Connect your test machine to Ethernet network. Run ifconfig and get Bcast address, for example 10.239.36.255....")
(mcts-connman-tests)
Line 1: Line 1:
= mcts-connman-tests =
= mcts-connman-tests =
-
1. Setup test environement
+
== Setup test environement ==
-
Ethernet network: Connect your test machine to Ethernet network. Run ifconfig and get Bcast address, for example 10.239.36.255.  
+
ConnMan deal with complex network environments. To test ConnMan, we have to setup test environment so that connman test suite can run on. Below diagram shows the ConnMan test environment:
-
    Make  sure 'ping -b 10.239.36.255' can get response. If not, you need setup another machine in this network to response broadcast
+
 
-
    ping. If the another machine is linux, you can make it work by 'echo "0" > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts'
+
 
-
  Bluetooth network: You need a bluetooth PANU server near your test machine. It can be an PANU AP, or a machine that provide PAN service.  
+
 
-
    Please refer to mcts-bluez-tests on how to setup a PANU server.
+
=== Different networks and connect to different networks===
-
  WiFi network: Setup a open hidden WiFi AP with essid "Guest"
+
+ Currently there are four networks: Ethernet/WiFi/Bluetooth/3G data networks<br/>
-
  All networks should provide DHCP service to automatically assign IP address. And can response broadcast ping.
+
+ dhcp enabled networks: All networks should be dhcp enabled so that test machine/server can get IP address. Basically your 3G/Wired network are dhcp enabled. And you need configure your WiFi/Bluetooth networks as dhcp enabled. You can set one of you WiFi AP as dhcp server. And we will discuss how to enable bluetooth server later<br/>
-
2. Run in test machine
+
+ Test server wire connects to Ethernet and WiFi networks. Test server actually provide Bluetooth PANU service<br/>
 +
+ Test machine wire connects to Ethernet. Test machine connects to WiFi/Bluetooth/3G networks through relative technologies<br/>
 +
 
 +
=== Test server configuration ===
 +
+ This is one time configuration, and you can use this configuration for all of your connman testing<br/>
 +
+ I use ubuntu 10.4 as test server in my environment this time<br/>
 +
+ I assume that IP address of test server as 192.168.*.1, please change accordingly<br/>
 +
+ Enable broadcast<br/>
 +
echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcast
 +
+ Setup a file for data transfer <br/>
 +
  mkdir -p /usr/share/mcts-connman-tests
 +
cd  /usr/share/mcts-connman-tests
 +
dd bs=1M count=10 if=/dev/zero of=10M
 +
+ Set up WiFi Aps with<br/>
 +
WiFi Open AP : essid: "Guest" and open no security
 +
WiFi WEP/PSK AP with essid and key that you defined.
 +
+ Setup Bluetooth server<br/>
 +
# Insert a bluetooth dongle
 +
git clone http://git.gitorious.org/meego-quality-assurance/mcts.git
 +
cp -r mcts/mct-bluez-tests/data/server /usr/local/bin/bluetooth
 +
/usr/local/bin/bluetooth/server_startup.sh &
 +
  /usr/local/bin/bluetooth/bt_pan_server_setup.sh &
 +
 
 +
# Setup dhcp server
 +
# edit /etc/default/dhcp3-server and add following line:
 +
INTERFACES="pan1"
 +
 
 +
  # edit /etc/dhcp3/dhcpd.conf and add following section:
 +
option subnet-mask 255.255.255.0;
 +
option broadcast-address 192.168.0.255;
 +
option routers 192.168.0.1;
 +
option domain-name-servers 192.168.0.1, 192.168.0.2;
 +
option domain-name "connman.org";
 +
 
 +
subnet 192.168.0.0 netmask 255.255.255.0 {
 +
range 192.168.0.10 192.168.0.200;
 +
}
 +
 
 +
== Run in test machine ==
  testrunner-lite -a -l '-testset=WiFiFeture' -f /usr/share/mcts-connman-tests/tests.xml -o results.xml
  testrunner-lite -a -l '-testset=WiFiFeture' -f /usr/share/mcts-connman-tests/tests.xml -o results.xml

Revision as of 07:16, 18 May 2011

Contents

mcts-connman-tests

Setup test environement

ConnMan deal with complex network environments. To test ConnMan, we have to setup test environment so that connman test suite can run on. Below diagram shows the ConnMan test environment:


Different networks and connect to different networks

+ Currently there are four networks: Ethernet/WiFi/Bluetooth/3G data networks
+ dhcp enabled networks: All networks should be dhcp enabled so that test machine/server can get IP address. Basically your 3G/Wired network are dhcp enabled. And you need configure your WiFi/Bluetooth networks as dhcp enabled. You can set one of you WiFi AP as dhcp server. And we will discuss how to enable bluetooth server later
+ Test server wire connects to Ethernet and WiFi networks. Test server actually provide Bluetooth PANU service
+ Test machine wire connects to Ethernet. Test machine connects to WiFi/Bluetooth/3G networks through relative technologies

Test server configuration

+ This is one time configuration, and you can use this configuration for all of your connman testing
+ I use ubuntu 10.4 as test server in my environment this time
+ I assume that IP address of test server as 192.168.*.1, please change accordingly
+ Enable broadcast

echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcast

+ Setup a file for data transfer

mkdir -p /usr/share/mcts-connman-tests
cd  /usr/share/mcts-connman-tests
dd bs=1M count=10 if=/dev/zero of=10M

+ Set up WiFi Aps with

WiFi Open AP : essid: "Guest" and open no security
WiFi WEP/PSK AP with essid and key that you defined.

+ Setup Bluetooth server

# Insert a bluetooth dongle
git clone http://git.gitorious.org/meego-quality-assurance/mcts.git
cp -r mcts/mct-bluez-tests/data/server /usr/local/bin/bluetooth
/usr/local/bin/bluetooth/server_startup.sh &
/usr/local/bin/bluetooth/bt_pan_server_setup.sh &
# Setup dhcp server
# edit /etc/default/dhcp3-server and add following line:
INTERFACES="pan1"
# edit /etc/dhcp3/dhcpd.conf and add following section:
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.1, 192.168.0.2;
option domain-name "connman.org";
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.10 192.168.0.200;
}

Run in test machine

testrunner-lite -a -l '-testset=WiFiFeture' -f /usr/share/mcts-connman-tests/tests.xml -o results.xml
Personal tools