[ell-i-developers] Re: Fwd: [riot-devel] Dedicated RIOT Testing Meeting // TODAY at 14 EET (13 CET)

  • From: Asif Sardar <engr.asif.sardar@xxxxxxxxxxxxxx>
  • To: "ell-i-developers@xxxxxxxxxxxxx" <ell-i-developers@xxxxxxxxxxxxx>
  • Date: Wed, 19 Nov 2014 16:55:55 +0200

Hi all,

Me and Teemu attended the meeting today with RIOT Team.

Here are the notes, I have been gathering. They will also provide a WiKi
link to the meeting results in their github, where everybody would add to
it the points that are missing.

***Automated Regression Testing***
-> Tests running on regular basis instead of every commit basis
-> Raspberry-pi (Master) with linux talks with CI build system, test whole
range of functionality
-> RF can be used to trigure the CI build system
-> Test feedback regarding test failures from daily build system
-> Automate hardware unit testing. In future, combine for integration
-> Problems related to pull request shall be addressed

-> Mainly simulations
-> Emulating the digital/discrete electronics
-> RIOT to be compiled on many compilers and many platforms
-> Support diverse building environment using different toolchains
-> Test suite run in docker container to be cross-platform
-> Making test system unified, by removing some bugs in multi-platform

***Documentation for RIOT APIs***
-> Nice and user friendly documentation for RIOT APIs

***RIOT Native***
-> Implements driver interface
-> Compile applications for riot and run on the native machine CPU
-> Emulate core level system functionality (no hardware/low-level emulation)
-> To make testing really fast and accessible, no flashing, no
hardware/driver/low-level issues
-> Network testing tool (virtual network interfaces, define networks to
debug RIOT netwrok stack API/software)

***Meeting Important Points Recap***
-> Distributed system, one central system (Raspberry-pi) communicating with
slave system (probably boards connected to CI server)
-> Run linux on both of them (Master and Slave), boards attached to slave
system, slave system reports back to master system connected to CI server
-> Testing individual boards can be trigured by commits in github
-> Tests slaves via RF integration into this distributed system and CI
-> Tests written in a way to run on any platform (native + actual board)
-> In CI server system, test library would have to decide if the tests can
be run against real hardware or native platform
-> Tests should work regardless of what CI system we use
-> Test executes on a system, system executes as much test as it can on
type of hardware or node it is attached to
-> Gather HW test results from slaves, deciding what hardware it is and
where it is attached to the CI system
-> Utilize codespeed in CI system (analyze the performance of your code)
-> Static code analyzers
   - cppcheck
   - Covertyscan some minor bugs
-> Using valgrind
-> Using only free/open-source software as much as we can
->* RF Tests on native, code quality using dynamic code analyzer. Providing
test coverage on unit tests and integration tests

Useful Links:

On Wed, Nov 19, 2014 at 11:55 AM, Teemu Hakala <temmi@xxxxxx> wrote:

> Hi all
> Sorry for the late announcement, but the folks at Riot OS are having a
> virtual meeting
> on the subject of testing. The software download link is below and I'll
> forward the actual
> meeting link when it is announced.
> Today, 14:00 Finnish time, 13:00 Central European time.
> Asif and I are going to be present. Asif has some material to present
> regarding what
> testing systems ELL-i has and where we have been thinking to go.
>  - t
> Begin forwarded message:
> *From: *Philipp Rosenkranz <philipp.rosenkranz@xxxxxxxxxxxx>
> *Subject: **Re: [riot-devel] Dedicated RIOT Testing Meeting*
> *Date: *11. marraskuuta 2014 22:13:23 UTC+2
> *To: *RIOT OS kernel developers <devel@xxxxxxxxxxx>
> *Reply-To: *RIOT OS kernel developers <devel@xxxxxxxxxxx>
> Hi everyone,
> I'd like to announce that the dedicated RIOT testing meeting will take
> place on:
> Wednesday the 19th of November at 01:00 pm CET.
> We will use PlaceCam for the meeting. If you are using Linux you need to
> install
> PlaceCam beforehand. PlaceCam can be found at [1].
> Please note that you don't need to create an PlaceCam account.
> Access to the conference call will be provided by a link which I will
> share on this
> list shortly before the meeting starts.
> [1] http://www.daviko.com/videokonferenz/3-1-Download.html
> Best regards,
> Philipp
> _______________________________________________
> devel mailing list
> devel@xxxxxxxxxxx
> http://lists.riot-os.org/mailman/listinfo/devel


*With Best Regards,Asif Sardar.+358 43 8265795*

Other related posts: