[ell-i-developers] Re: Robot Framework Testing: Test Cases Design, Scripting and other Issues

From: Asif Sardar <engr.asif.sardar@xxxxxxxxxxxxxx>
To: Pekka Nikander <pekka.nikander@xxxxxx>, ell-i-developers@xxxxxxxxxxxxx
Date: Tue, 1 Jul 2014 17:39:09 +0300
Hello,

Emulator is gradually getting matured to work with robot framework test
cases. The test cases for serial communication are now working for the
emulator. The current runtime is not fully implemented, hence some of the
serial communication tests cannot be run. However, the old runtime contains
the working serial communication implementation.

The next important task would be to test the timers with emulator and also
merge the serial communication functionality from old runtime to current
runtime simultaneously.

BR,
Asif Sardar.


On Tue, Jul 1, 2014 at 5:38 PM, Asif Sardar <engr.asif.sardar@xxxxxxxxxxxxxx
> wrote:

> Hello,
>
> Emulator is gradually getting matured to work with robot framework test
> cases. The test cases for serial communication are now working for the
> emulator. The current runtime is not fully implemented, hence some of the
> serial communication tests cannot be run. However, the old runtime contains
> the working serial communication implementation.
>
> The next important task would be to test the timers with emulator and also
> merge the serial communication functionality from old runtime to current
> runtime simultaneously.
>
> BR,
> Asif Sardar.
>
>
> On Fri, Jun 13, 2014 at 3:19 PM, Asif Sardar <
> engr.asif.sardar@xxxxxxxxxxxxxx> wrote:
>
>> > Right, changing the output register does not change the input register,
>> ever.  It would be quite easy to implement that, but I didn't do anything
>> like that.
>> > The only slot I have any more available is Wednesday 10:30-13:00, and
>> I should have also lunch then.  That we can take for pair coding.  Should
>> we?
>>
>> Lets meet Wednesday between 10:30 - 12:30, then lunch and after that our
>> Wednesday meeting from 13:00 - 14:30. During, this pair coding we can
>> discuss about further meeting after midsummer.
>>
>>
>> On Thu, Jun 12, 2014 at 7:11 PM, Pekka Nikander <pekka.nikander@xxxxxx>
>> wrote:
>>
>>> > It seems that the GPIO peripherals for the emulator does not store the
>>> states for input/output and also doesn't store states for the different
>>> registers e,g, PUPDR, IDR, BSR, BSRR, MODER and AFR etc.
>>>
>>> You are right, the emulator does not store or emulate the input/output
>>> state.  However, it should store the state of the individual registers, but
>>> not any dependencies between them.
>>>
>>> > For example. to test DigitalRead() for a pin, I changed the pin mode
>>> to output, made pin high, change mode to input and read value from same
>>> pin, it didn't affect the pin state!
>>>
>>> Right, changing the output register does not change the input register,
>>> ever.  It would be quite easy to implement that, but I didn't do anything
>>> like that.
>>>
>>> > Pekka, can we have one or two sessions during next week (pair coding
>>> etc) to know more about emulator and test cases issues.
>>>
>>> Well, yes, we should, but not easily next week.  The only slot I have
>>> any more available is Wednesday 10:30-13:00, and I should have also lunch
>>> then.  That we can take for pair coding.  Should we?
>>>
>>> On the week after midsummer (starting Mon the 23rd), I should have 1-2
>>> days available.  I'm not quite sure which ones, but tentatively we could
>>> agree on Wednesday and Thursday mornings, say 8:30-11:30 both days.  Would
>>> that work for you?
>>>
>>> > In the meanwhile I can change all the test library scripts to load
>>> emulator instead of using the python-c modules (done previously the hard
>>> way). Moreover, I can also plan out the input/output types from python
>>> ctypes module for the libemulator.so function calls, also because we
>>> haven't find way to include header files in the python script. Also, I can
>>> have a look at call back routines from python ctypes module, if there are
>>> any! so that we can return to test library scripts from emulator
>>> peripherals.
>>>
>>> Sounds good!  Please continue the good initiatives!
>>>
>>> --Pekka
>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *With Best Regards,Asif Sardar.+358 43 8265795 <%2B358%2043%208265795> *
>>
>
>
>
> --
>
>
>
> *With Best Regards,Asif Sardar.+358 43 8265795 <%2B358%2043%208265795>*
>



-- 



*With Best Regards,Asif Sardar.+358 43 8265795*
[ell-i-developers] Re: Robot Framework Testing: Test Cases Design, Scripting and other Issues

Other related posts:
