bluval engine refactoring 63/563/17
authorNaga Sugguna <ns156u@att.com>
Wed, 17 Apr 2019 12:56:05 +0000 (07:56 -0500)
committerNaga Sugguna <ns156u@att.com>
Fri, 24 May 2019 13:11:06 +0000 (13:11 +0000)
commit0469b07ecc803e7a0ba91474d916fa3cf5aacd4c
treef9702cb6fc16b00518c0387cbb264d092351b72c
parentc9557c979fe276c61b4b90b9885ff532e25cbc26
bluval engine refactoring

actual .robot testcases used instead of helloworld
bluval-dummy.yaml is added for dummy blue print to test easily
All the rebot results redirected to one directory results
click is used to take parameters from CLI
optional --layer/l is taken as parameter
Deriving yaml location from blue print name
Sections named as layers and layer names expanded hw -> hardware
.py code refactored, mode functions added.

Change-Id: Id916a79301d32ed64afc398fb486ba71b81a1dea
Signed-off-by: Naga Sugguna <ns156u@att.com>
bluval/bluval-base.yaml
bluval/bluval-dummy.yaml [new file with mode: 0644]
bluval/bluval.py
bluval/requirements.txt