http://bugzilla.moblin.org/show_bug.cgi?id=9862





--- Comment #2 from pohly <[email protected]>  2010-03-16 09:50:53 PST ---
(In reply to comment #1)
> I have a preview version available in mb9862 branch, except the with/witout
> ctcap not yet implemented.
> 
> Is the options look OK?

The options are almost okay.

>   -b BTADDR, --bt-address=BTADDR
>                         The bluetooth mac address for the testing phone

Bluetooth

>   -s SOURCE, --source=SOURCE
>                         The local database for testing, cab be one of
>                         contacts|calendar|task|memo, by default it will try
>                         all one by one

"cab" -> "can"

>   -u URL, --url=URL     The url for testing the selected source

"URL" -> "URI"

"Invalid unless a specific source is selected"?

>   -t TYPE, --type=TYPE  The content type for testing the selected source

"Invalid unless a specific source is selected"? What is tested when not
specified?

>   -i IDENTIFIER, --identifier=IDENTIFIER
>                         The identifier used when contacting the phone

Again, what is tested automatically?

>   --without-ctcap       Testing without sending CTCap information
>   -v, --verbose         Enabling detailed output

When verbose is off, what is the output? After a quick glance at the
implementation it seems that the result of the tool is not printed when verbose
is off. That would render non-verbose runs almost useless.

The test config uses the default context and thus the default
backends/databases. Don't! The user might have valid data there which would be
affected by running the script. Use the "file" backend and some temp
directories in /tmp/ instead, configured with a custom context. Clean up as
much as possible when the script terminates, including removal of the config.

Missing: combined calendar+todo on/off. Actually sending and receiving data.

-- 
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

Reply via email to