GSM unit test - Revision history

Glenn: -Category:OpenMoko (Category:Test is enough)

2008-03-18T12:30:21Z

-Category:OpenMoko (Category:Test is enough)

Coolcat at 04:32, 13 March 2008

2008-03-13T04:32:03Z

Erin: /* How to use this python script */

2008-02-20T06:57:30Z

‎How to use this python script

Erin: /* How to use this python script */

2007-12-07T10:34:50Z

‎How to use this python script

Erin: /* How to use this python script */

2007-12-04T09:35:01Z

‎How to use this python script

Erin: /* text format */

2007-12-04T09:14:52Z

‎text format

Erin: /* how to write expect list to match the result */

2007-12-04T09:13:43Z

‎how to write expect list to match the result

Erin: /* how to write expect list to match the result */

2007-12-04T09:13:17Z

‎how to write expect list to match the result

Erin: /* how to write expect list to match the result */

2007-12-04T07:25:17Z

‎how to write expect list to match the result

Erin: /* GSM unit test */

2007-12-04T06:26:43Z

‎GSM unit test

@@ Line 51: / Line 51: @@
 * script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.
-[[Category:OpenMoko]]
 [[Category:Test]]

← Older revision		Revision as of 04:32, 13 March 2008
Line 51:		Line 51:

	* script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.		* script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.
		+	[[Category:OpenMoko]]
		+	[[Category:Test]]

@@ Line 5: / Line 5: @@
 == How to use this python script ==
-* python script  [[http://cs.nyu.edu/~wcy203/UnitTestv2.py  1]]
+* python script  [[http://people.openmoko.org/erin_yueh/UnitTestv2.py  1]]
-* sample test case  [[http://cs.nyu.edu/~wcy203/casev1 2]]
+* sample test case  [[http://people.openmoko.org/erin_yueh/casev1 2]]
 * register the network test case [[http://cs.nyu.edu/~wcy203/RegistertoNetwork 3]]
-* dial out test case [[http://cs.nyu.edu/~wcy203/DialOut 4]]
+* dial out test case [[http://people.openmoko.org/erin_yueh//DialOut 4]]
-* send/receive SMS test case  [[http://cs.nyu.edu/~wcy203/SendReceiveSMS 5]]
+* send/receive SMS test case  [[http://people.openmoko.org/erin_yueh/SendReceiveSMS 5]]
    usage:  python UnivTestv1.py  -t  casename  -c  libgsmd-tool  -m  shell

@@ Line 5: / Line 5: @@
 == How to use this python script ==
-  code is [[http://cs.nyu.edu/~wcy203/UnitTestv2.py  here]]
+* python script  [[http://cs.nyu.edu/~wcy203/UnitTestv2.py  1]]
- sample test case is [[http://cs.nyu.edu/~wcy203/casev1 here]]
+* sample test case  [[http://cs.nyu.edu/~wcy203/casev1 2]]
    usage:  python UnivTestv1.py  -t  casename  -c  libgsmd-tool  -m  shell

@@ Line 5: / Line 5: @@
 == How to use this python script ==
-   code is [[ here]]
+   code is [[http://cs.nyu.edu/~wcy203/UnitTestv2.py  here]]
-  sample test case is [[here]]
+  sample test case is [[http://cs.nyu.edu/~wcy203/casev1 here]]
    usage:  python UnivTestv1.py  -t  casename  -c  libgsmd-tool  -m  shell

@@ Line 20: / Line 20: @@
   C:r
   E:Register,error
-  E:Netreg registered(home network),error,OK
+  E:Netreg registered(home network),OK,error
-−
   From above case, it sends 'r' command to libgsmd-tool and it tries to register the network.

@@ Line 36: / Line 36: @@
 From above real output from libgsmd-tool, it's very easy to detect the expect behavior. The first expect, it prints the command descriptions. The second expect, we can use some keywords like 'Netreg registered' for this case.
- * use ',' for the delimiter
+* use ',' for the delimiter
- * always put the most matched one on the first element: There can be a lot of matched elements in an expect list.  Put this list before using 'error'
+* always put the most matched one on the first element: There can be a lot of matched elements in an expect list.  Put this list before using 'error'
- * append .EOF and .TIMEOUT elements to the expect list: When it reads the second expect line, it appends these two more elements to the list.
+* append .EOF and .TIMEOUT elements to the expect list: When it reads the second expect line, it appends these two more elements to the list.
- * how to know it's failed or passed:  there are 4 cases
+* how to know it's failed or passed:  there are 4 cases
- # correct: passed
+# correct: passed
- # error: failed
+# error: failed
- # EOF: failed
+# EOF: failed
- # timeout: failed
+# timeout: failed
- * script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.
+* script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.

@@ Line 35: / Line 35: @@
 ==== how to write expect list to match the result ====
 From above real output from libgsmd-tool, it's very easy to detect the expect behavior. The first expect, it prints the command descriptions. The second expect, we can use some keywords like 'Netreg registered' for this case.
 *always put the most matched one on the first element: There can be a lot of matched elements in an expect list. For this python script, please put the most matched element on the expect list.

@@ Line 36: / Line 36: @@
 From above real output from libgsmd-tool, it's very easy to detect the expect behavior. The first expect, it prints the command descriptions. The second expect, we can use some keywords like 'Netreg registered' for this case.
-==== always put the most matched one on the first element ====
+*always put the most matched one on the first element: There can be a lot of matched elements in an expect list. For this python script, please put the most matched element on the expect list.
 There can be a lot of matched elements in an expect list. For this python script, please put the most matched element on the expect list.
-==== append .EOF and .TIMEOUT elements to the  expect list ====
+*append .EOF and .TIMEOUT elements to the  expect list:  When it reads the second expect line, it appends these two more elements to the list.
 When it reads the second expect line, it appends these two more elements to the list.
-==== how to know it's failed or passed ====
+*how to know it's failed or passed: After sending a command, it will print correct. if it's passed.  If it's failed, it will print Timeout on the screen
-After sending a command, it will print <b>'correct'</b> if it's passed.  If it's failed, it will print <b>'Timeout'</b> on the screen
-==== script log ====
+*script log: It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.
 It also stores the session log from 'libgsmd-tool', and the default file name is 'script.log'.