Hi,

As you might have noticed on gerrit,
I've been trying to establish tests with SECURED mode on jenkins for a week.

This is just done on master branch, (and partially on 1.2-rel : only 
resource)

I also have created at wiki page, where anyone can share tips about 
testing, debuging etc:

https://wiki.iotivity.org/wiki/test

But today I used it to propose a policy to
fix and track UT in "resource" codebase ASAP (in master 1st)

Copy of current version is following,
Of course at this plan can be discussed at:
https://jira.iotivity.org/browse/IOT-1486

Thanks again for your patience.


==== USAGE ====

   ./autobuild.py unit_tests

==== STATUS ====

=== 2016-12-13 ===

Jenkins (CI) will run unit_tests on linux with SECURED=0 and SECURED=1 
on master branch
for all subsystems (currently service and resource 
https://gerrit.iotivity.org/gerrit/#/c/15291/).

Some tests have been bypassed because they are failing,
leaking memory or not terminating, so they need to be fixed by developers.

So let's try to fix "resource" codebase first in master branch first,
then pick patches to  [[1.2-rel]] branch,
for "service" codebase it can be more relaxed (bypass) in shorter term.

All unit tests should support all CI configurations flags (or most, ie: 
SECURED=0 and SECURED=1 modes).
If not possible then they need to be bypassed in code or better in scons 
file (like I did),
please comment explicitly why a configuration can't be supported (or 
report bug and link it).

Current UT issues to be investigated can be found easily using this 
simple command:

On master branch ([[1.2-rel]] as well):

<code>
find . -iname "SConscript" -exec grep -H 'TODO' {} \; | grep -i test

./resource/provisioning/unittests/SConscript:# TODO: Fix test for 
supported configurations
./resource/unittests/SConscript:# TODO: Fix errors in the following 
Windows tests.
./resource/csdk/SConscript:    # TODO: Switch Linux to use a Static 
library for testing like every other OS.
./resource/csdk/connectivity/test/SConscript:# TODO: fix test in 
supported configurations
./resource/csdk/resource-directory/unittests/SConscript:# TODO: fix test 
for all supported configurations
./resource/csdk/resource-directory/unittests/SConscript:# TODO: fix this 
test on linux and remove this comment line
./resource/csdk/security/provisioning/unittest/SConscript:# TODO: fix 
test for all supported configurations
./resource/csdk/security/unittest/SConscript:   # TODO: Implement 
feature check.
./resource/csdk/stack/test/SConscript:# TODO: fix test in all supported 
configurations
</code>


If your module is in this list, then you're welcome to "take" this task
and let it know on this "temporary" wiki page: 
https://wiki.iotivity.org/wiki/test

   * comment here (can be a gerrit url or jira id, whatever)

Once done remove TODO and related commented lines
and make sure to pass memcheck file to valgrind to track memory leaks.

-- 
mailto:philippe.coval at osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/

Reply via email to