On 04.04.2014 03:25, Denis Kenzior wrote:
>> The number of modems returned by org.ofono.Manager.GetModems() must
>> represent the total number of modems available to the system and thus we
>> need to have exactly two modems when testing dual-sim features etc.
>>
>
> Sounds like your system is a bi
On 04.04.2014 03:11, Denis Kenzior wrote:
> Hi Antti,
>
>> Oh, didn't know that. That sounds great!
>> We were under the impression that the phonesim instances have to be
>> running before phonesim plugin loads and the modem .xml configurations
>> can't be changed on the fly.
>
> What modem .xml
Hi Antti,
> What we are trying to do is a full stack system testing where the
> individual components that are being tested don't have any modifications
> or adaptations when they are run under test suite.
Okay that sort of makes sense
>
> The number of modems returned by org.ofono.Manager.GetM
Hi Antti,
On 04/03/2014 07:09 PM, Antti Kaijanmäki wrote:
> On 04.04.2014 02:45, Antti Kaijanmäki wrote:
>> Only if the file exists phonesim plugin would then create a _listening_
>> socket on the specified port.
>
> Actually, are plugins able to register arbitrary dbus-objects under
> org.ofono?
Hi Antti,
> Oh, didn't know that. That sounds great!
> We were under the impression that the phonesim instances have to be
> running before phonesim plugin loads and the modem .xml configurations
> can't be changed on the fly.
What modem .xml configurations? I'm lost now.
You have phonesim plug
On 04.04.2014 00:40, Denis Kenzior wrote:
> Phonesim can have an arbitrary number of instances (I once tested 100 at
> once), and one can assign an object path using phonesim.conf. Your test
> application can then find such groupings and accomplish essentially the
> same thing as you're trying to
On 04.04.2014 02:45, Antti Kaijanmäki wrote:
> Only if the file exists phonesim plugin would then create a _listening_
> socket on the specified port.
Actually, are plugins able to register arbitrary dbus-objects under
org.ofono?
Something like /phonesim with an org.ofono.phonesim.Control interfa
On 04.04.2014 00:40, Denis Kenzior wrote:
> Hi Antti,
>>
>> Indeed, and this combined with commit 5f765259 one can easily run a
>> series of tests (let's say dialer UI, messaging..) with different
>> phonesim configurations changing the number of modems and phonesim .xml
>> files for each modem.
>
On 03.04.2014 20:55, Marcel Holtmann wrote:
>> Indeed, and this combined with commit 5f765259 one can easily run
>> a series of tests (let's say dialer UI, messaging..) with
>> different phonesim configurations changing the number of modems and
>> phonesim .xml files for each modem.
>
> this argum
Hi Antti,
>
> Indeed, and this combined with commit 5f765259 one can easily run a
> series of tests (let's say dialer UI, messaging..) with different
> phonesim configurations changing the number of modems and phonesim .xml
> files for each modem.
I see what you needed that commit for now. While
Hi Jussi,
In testing it is sometimes useful to be able to replace the system
ofono daemon instance with our own. This patch makes this possible
using dbus' name replacement feature. This patch has the plumbing
changes to make it possible to set the name replacement settings.
>>
Hi Jussi,
>>> In testing it is sometimes useful to be able to replace the system
>>> ofono daemon instance with our own. This patch makes this possible
>>> using dbus' name replacement feature. This patch has the plumbing
>>> changes to make it possible to set the name replacement settings.
>>> Th
On 03.04.2014 10:38, Jussi Pakkanen wrote:
> On 02.04.2014 21:39, Marcel Holtmann wrote:
>
>>> In testing it is sometimes useful to be able to replace the system
>>> ofono daemon instance with our own. This patch makes this possible
>>> using dbus' name replacement feature. This patch has the plum
On 02.04.2014 21:39, Marcel Holtmann wrote:
In testing it is sometimes useful to be able to replace the system
ofono daemon instance with our own. This patch makes this possible
using dbus' name replacement feature. This patch has the plumbing
changes to make it possible to set the name replacem
Hi Jussi,
> In testing it is sometimes useful to be able to replace the system ofono
> daemon
> instance with our own. This patch makes this possible using dbus' name
> replacement
> feature. This patch has the plumbing changes to make it possible to set the
> name replacement settings. The next
From: Jussi Pakkanen
Hello
In testing it is sometimes useful to be able to replace the system ofono daemon
instance with our own. This patch makes this possible using dbus' name
replacement
feature. This patch has the plumbing changes to make it possible to set the
name replacement settings. Th
16 matches
Mail list logo
