http://bugzilla.moblin.org/show_bug.cgi?id=9862
--- Comment #3 from Chen Congwu <[email protected]> 2010-03-25 23:57:13 PST --- (In reply to comment #2) New version: limitations: --ctcap is not implemented, Patrick what do you think is the appropriate approach for this? Can I add a environment variable for this (eg. SYNCEVOLUTION_TEST_NOCTCAP), or should the test tool copy the template base file (syncevolution.xml) and modify it on the fly? --advanced When testing with real data, I leveraged client-test (testCopy) for this. The problem is it usually fails for a phone because of some data mismatch (especially for calendar data). The options might not be as useful enough because it will even wipes the data on the phone. --------- python ../test/test-phone.py --help Usage: test-phone.py [options] Options: -h, --help show this help message and exit -b BTADDR, --bt-address=BTADDR The Bluetooth mac address for the testing phone -p VERSION, --proto-version=VERSION The SyncML protocal version for testing, can be one of 1.0|1.1|1.2, by default it will try all versions one by one -s SOURCE, --source=SOURCE The local database for testing, can be one of contacts|calendar|task|memo|calendar+task, by default it will try all except calendar+task, use --combined- calendar-task to activate -u URI, --uri=URI The URI for testing the selected source, invalid when no specific source is selected via --source -t TYPE, --type=TYPE The content type for testing the selected source, invalid when no specific source is selected via --source -i IDENTIFIER, --identifier=IDENTIFIER The identifier used when contacting the phone, can be arbitray string. By default it will try 'PC Suite','Nokia PC Suite' and empty string --without-ctcap Testing without sending CTCap information -v, --verbose Enabling detailed output --combined-calendar-task Testing the combined calendar, task data source -a, --advanced More extensive test with sending/receving data, this requires installing syncevolution-test package and it may destroy your data on the tested phone Output for the Nokia N900: python ../test/test-phone.py -b FF:FF:FF:FF:FF:FF -i 'PC Suite' -p 1.2 Starting test for 116 configurations... Start 1/116 test Start 2/116 test Start 3/116 test Start 4/116 test Start 5/116 test Found a working configuration for contact Test 6/116 skipped Test 7/116 skipped Test 8/116 skipped Test 9/116 skipped Test 10/116 skipped Test 11/116 skipped Test 12/116 skipped Test 13/116 skipped Test 14/116 skipped Test 15/116 skipped Test 16/116 skipped Test 17/116 skipped Test 18/116 skipped Test 19/116 skipped Test 20/116 skipped Test 21/116 skipped Test 22/116 skipped Test 23/116 skipped Test 24/116 skipped Start 25/116 test Found a working configuration for calendar Test 26/116 skipped Test 27/116 skipped Test 28/116 skipped Test 29/116 skipped Test 30/116 skipped Test 31/116 skipped Test 32/116 skipped Test 33/116 skipped Test 34/116 skipped Test 35/116 skipped Test 36/116 skipped Test 37/116 skipped Test 38/116 skipped Test 39/116 skipped Test 40/116 skipped Start 41/116 test Found a working configuration for task Test 42/116 skipped Test 43/116 skipped Test 44/116 skipped Test 45/116 skipped Test 46/116 skipped Test 47/116 skipped Test 48/116 skipped Test 49/116 skipped Test 50/116 skipped Test 51/116 skipped Test 52/116 skipped Test 53/116 skipped Test 54/116 skipped Test 55/116 skipped Test 56/116 skipped Test 57/116 skipped Test 58/116 skipped Test 59/116 skipped Test 60/116 skipped Test 61/116 skipped Test 62/116 skipped Test 63/116 skipped Test 64/116 skipped Test 65/116 skipped Test 66/116 skipped Test 67/116 skipped Test 68/116 skipped Test 69/116 skipped Test 70/116 skipped Test 71/116 skipped Test 72/116 skipped Test 73/116 skipped Test 74/116 skipped Test 75/116 skipped Test 76/116 skipped Test 77/116 skipped Test 78/116 skipped Test 79/116 skipped Test 80/116 skipped Start 81/116 test Start 82/116 test Start 83/116 test Start 84/116 test Start 85/116 test Start 86/116 test Start 87/116 test Found a working configuration for memo Test 88/116 skipped Test 89/116 skipped Test 90/116 skipped Test 91/116 skipped Test 92/116 skipped Test 93/116 skipped Test 94/116 skipped Test 95/116 skipped Test 96/116 skipped Test 97/116 skipped Test 98/116 skipped Test 99/116 skipped Test 100/116 skipped Test 101/116 skipped Test 102/116 skipped Test 103/116 skipped Test 104/116 skipped Test 105/116 skipped Test 106/116 skipped Test 107/116 skipped Test 108/116 skipped Test 109/116 skipped Test 110/116 skipped Test 111/116 skipped Test 112/116 skipped Test 113/116 skipped Test 114/116 skipped Test 115/116 skipped Test 116/116 skipped Test Ended ****************SUMMARY**************** ------------------------------------------ Configuration parameter for calendar: Test parameter: With CTCap: True Identifier: PC Suite SyncML version: 1.2 Sync Source: calendar URI: Calendar Content Type: text/calendar:2.0 ------------------------------------------ Configuration parameter for contact: Test parameter: With CTCap: True Identifier: PC Suite SyncML version: 1.2 Sync Source: contact URI: Contacts Content Type: text/vcard:3.0 ------------------------------------------ Configuration parameter for memo: Test parameter: With CTCap: True Identifier: PC Suite SyncML version: 1.2 Sync Source: memo URI: Notes Content Type: text/plain:1.0 ------------------------------------------ Configuration parameter for task: Test parameter: With CTCap: True Identifier: PC Suite SyncML version: 1.2 Sync Source: task URI: Calendar Content Type: text/calendar:2.0 Note some phones have combined calendar and task you might run the tool with --combined-calendar-task to detect this behavior This phone likely works with a combined calendar and task because they have identical configurations -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
