Closed Bug 1016773 Opened 11 years ago Closed 11 years ago

Test case for default route switch

Categories

(Firefox OS Graveyard :: Wifi, defect)

Product:
Firefox OS Graveyard
Component:
Wifi
Platform:
x86_64
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID
Milestone:
2.0 S3 (6june)

People

(Reporter: hchang, Assigned: hchang)

Details

(Whiteboard: [p=2])

When wifi and mobile connection are both enabled, the routing table on emulator should look like: root@android:/ # netcfg lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00 eth0 UP 10.0.2.15/24 0x00001043 52:54:00:12:34:56 rmnet1 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:58 rmnet2 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:59 rmnet3 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:5a wlan0 UP 10.0.2.15/24 0x00001043 52:54:00:12:34:5b sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00 rmnet0 DOWN 10.0.2.100/24 0x00001002 52:54:00:12:34:57 After turning off wifi, it should look like the following: root@android:/ # netcfg lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00 eth0 UP 10.0.2.15/24 0x00001043 52:54:00:12:34:56 rmnet1 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:58 rmnet2 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:59 rmnet3 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:5a wlan0 DOWN 0.0.0.0/0 0x00001002 52:54:00:12:34:5b sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00 rmnet0 UP 10.0.2.100/24 0x00001043 52:54:00:12:34:57 We can have a test case to test if rmnet0 becomes UP and ip is set to '10.0.2.100'
Assignee: nobody → hchang
Whiteboard: [p=2]
Target Milestone: --- → 2.0 S3 (6june)
I believe what this bug would like to test is already covered by the integration tests for wifi tethering.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.