summaryrefslogtreecommitdiffstats
path: root/test-widget/test-config.xml.in
AgeCommit message (Collapse)AuthorFilesLines
2018-10-19Always use wgt when talking about widgetRomain Forlot1-25/+0
We already have a wgt directory so this just make use the same for the test widget directory. Change-Id: I2eb5c7a4faf17adb8f011b7e37ac98389340d41b Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2018-10-16Use a custom test-config.xml file for test widgetRomain Forlot1-1/+1
Bug-AGL: SPEC-1821 Change-Id: If664757a7dec8e43cd8f4776bab16d026e583752 Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2018-08-16Rollback about TEST build typeRomain Forlot1-1/+1
This implies to much side effects over a complete AGL image build. So it's better to not affect the CMAKE_BUILD_TYPE variable to determine wether or not the test WGT file is generated. Change-Id: I77e8bdb085d164a4dd387ac48c425c011840473b Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2018-08-03Create a test widgetRomain Forlot1-0/+25
Create a test widget in addition of the normal one when you use any build type except of RELEASE. This widget will only provide the test files (configuration + test + fixtures ...). It joins the test framework binding to your binding or app then you only have to access to your defined test API and launch the tests. The entry point is a bash script which is in charge to launch all tests it finds. Change-Id: I8f4a670f17fd4e4319c53a861074fb5e10b63aad Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>