I rebase my DUN patches with latest git tree and combine them here. For some reason, I cann't continue to work on this feature. I hope someone interested about it could pick up these patches and continue this work.
Please feel free to give your comments.
when I install the ofono, I have problems. I use the ofono-0.26 and set up the ofono process ,come into the "test" dir.At the first ,I use the ./enable-modem command .Secondly, when i use the ./test-voicecall /generic 10086,it show error.The error is that the operation failed .I trace the code,the var in the atd_cb funaction show that ok=0. IF ok=0,the function goto error.I don not know the reasion.
I look forward to contacting to me.Please send the reasion to the email:firstname.lastname@example.org.
I have been trying an Option modem with ofono recently.
It took me a while to establish a connection because the APN
we're using needs a username and password. Apparently Option
swapped the username and password of the AT command AT$QCPDPP.
Also, it seems that some other Option modem uses AT_OPDPP
instead of AT$QCPDPP, see http://www.pharscape.org/Quicksilver.html
I'll send two patches in reply to this message. The first one
adds username and password optional parameters to
test/create-context. And the second one swaps username and
password for hso modem in PAP mode.
Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ?
Je crée ma boîte mail www.laposte.net
Phonesim is most of time a convenient way to test oFono. For example, it can be used to test MO call, as well as MT call.
And talking about test area, test automation is quite important regarding to both efficiency and effectiveness. In the test of MO call, scripts can be used to interact with oFono via D-Bus to make test automation possible. However, in the test of MT call, currently we have to enter the caller number and click some button in Phonesim GUI to simulate an incoming call, which makes test automation unrealistic.
With this patch, Phonesim can work in the following way:
1. It observes some specific directory (/tmp/scripts) to see if there is some test scripts added.
2. Once Phonesim finds a new test script is added, it will parse and execute the script.
3. You may add more and more test scripts to the specific directory with your test goes on.
Below are two examples:
# call.js (Simulate a MT call)
tabRegistration.gbIncomingCall.leCaller.text = "12345";
This script will help you enter the caller number as "12345", and click "Call" button in Phonesim GUI. Once this script is copied to the observed directory, oFono will get an incoming call.
# sms.js (Simulate a MT sms)
tabSMS.gbMessage1.leMessageSender.text = "Yang";
tabSMS.gbMessage1.leSMSClass.text = "1";
tabSMS.gbMessage1.teSMSText.setPlainText("This message is sent automatically from Phonesim");
This script will help you fill the sms sender, class, text, and then click the "Send Message" button for you. Once it's added into the specific directory, oFono will get an incoming message.
Don't know if this is the best way to make Phonesim support test automation. So comments are welcome:)
Yang Gu (1):
Enable Qt Script
configure.ac | 2 +-
src/control.cpp | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 61 insertions(+), 1 deletions(-)