anchor.diff:  TestScript,documentation_Configuration_Management_FW_Design,Documentation,To check the docs of Configuration Management FW Design,1,Check the doc ,the doc has content about the design of Configuration Management FW ,FVT,ready,IOTOS-711,,,,
   TestScript,Boot Mode auto chosen,Software Update,Select a bootloader that can dynamically choose the boot mode,1,check related docs ,verify that uefi stub is selected for uefi compatible machines and uboot for the rest,FVT,ready,IOTOS-743,,,,
   TestScript,CI_Monitor_Multi_branch,SCM / Backend Services Configuration,To check CI can monitor multi-branches to build image,1,check branches in ostro-os repo,See multi-branches,FVT,ready,IOTOS-782,,,,
  -TestScript,build_uninative_tarball,eSDK,build uninative tarball,1,"fetch ostro-os source codes and build uninative tarball with command: SDKMACHINE=""x86_64""(""i586"" for 32 bit) bitbake uninative-tarball",FVT,ready,IOTOS-1208,,,,,
  +TestScript,build_uninative_tarball,eSDK,build uninative tarball,1,"fetch ostro-os source codes and build uninative tarball with command: SDKMACHINE=""x86_64""(""i586"" for 32 bit) bitbake uninative-tarball",,FVT,ready,IOTOS-1208,,,,
   TestStep,,,,2,check the 64bit/32bit uninative tarball can be built out,,,,,,,,
  -TestScript,verify_host_agnostic_native_env,eSDK,deploy uninative tarball in host environment,1,deploy the uninative tarball on web server and generate MD5 checksum,FVT,ready,IOTOS-1208,,,,,
  +TestScript,verify_host_agnostic_native_env,eSDK,deploy uninative tarball in host environment,1,deploy the uninative tarball on web server and generate MD5 checksum,,FVT,ready,IOTOS-1208,,,,
   TestStep,,,,2,create test project recipe with devtool,,,,,,,,
   TestStep,,,,3,"configure the test project .bb file with adding: ""INHERIT += ""uninative"" UNINATIVE_URL = ""http://ostro/sdk/"" UNINATIVE_CHECKSUM[x86_64] = ""a3c09c01688b560d1512600487e0f3a0""""",,,,,,,,
   TestStep,,,,4,build test project with bitbake,PASS if the build process succeed and no need to build any native component in the progress,,,,,,,
  -TestScript,appfw_add_preinstall_app,AppFW/app,Use bitbake to pre-install example app to image,1,"Edit ostro-os code, build/conf/local.conf, to add: IMAGE_INSTALL_append = "" example-app-node""",,FVT,design,IOTOS-337,,,,
  +TestScript,appfw_add_preinstall_app,AppFW/app,Use bitbake to pre-install example app to image,1,"Edit ostro-os code, build/conf/local.conf, to add: IMAGE_INSTALL_append = "" example-app-node""",,FVT,ready,IOTOS-337,,,,
   TestStep,,,,2,bitbake ostro-image and boot up. ,"There should be /apps/iodine , which is in example-app-node app.",,,,,,,
  -TestScript,appfw_launch_preinstall_app,AppFW/app,launch the pre-installed example app,1,systemctl start iodine-nodetest.service,,FVT,design,IOTOS-337,,,,
  +TestScript,appfw_launch_preinstall_app,AppFW/app,launch the pre-installed example app,1,systemctl start iodine-nodetest.service,,FVT,ready,IOTOS-337,,,,
   TestStep,,,,3,Check if the example app is running,"Do 'ps', search if iodine-nodetest works as a daemon",,,,,,,
  -TestScript,appfw_container_autolaunch,AppFW/app,The container is automatically launched when launching app,1,systemctl start iodine-nodetest.service,,FVT,design,IOTOS-342,,,,
  +TestScript,appfw_container_autolaunch,AppFW/app,The container is automatically launched when launching app,1,systemctl start iodine-nodetest.service,,FVT,ready,IOTOS-342,,,,
   TestStep,,,,2,Check 'journalctl -a' to see if the container is launched,"There is ""Started Container iodine-nodetest"" in the journeyctl log",,,,,,,
  -TestScript,appfw_container_status,AppFW/app,Read container status ,1,systemctl start iodine-nodetest.service,,FVT,design,IOTOS-342,,,,
  +TestScript,appfw_container_status,AppFW/app,Read container status ,1,systemctl start iodine-nodetest.service,,FVT,ready,IOTOS-342,,,,
   TestStep,,,,2,Check 'machinectl status iodine-nodetest' to see container information,"Check 'Leader', it should show the correct PID of the app",,,,,,,
  -TestScript,appfw_nonroot_uid,AppFW/app,check application is launched by non-root UID,1,systemctl start iodine-nodetest.service,,FVT,design,IOTOS-339,,,,
  +TestScript,appfw_nonroot_uid,AppFW/app,check application is launched by non-root UID,1,systemctl start iodine-nodetest.service,,FVT,ready,IOTOS-339,,,,
   TestStep,,,,2,"Run 'ps', check /lib/node_modules/nodetest/example.js daemon's uid",The uid of the daemon should not be root,,,,,,,
   TestScript,appfw_neg_app_impersonation,AppFW/app,one app's user should not pretend to be another's user,1,Install at least two example applications into image.,,FVT,ready,IOTOS-416,,,,
   TestStep,,,,2,"After system boots up, find two user id of the two example apps under /home folder. ",The two new user name should be found under /home/,,,,,,,
  
positive.code: # su App1    (App1 is the user name string of 1st example app)","Now, you are in App1 account.",,,,,,,
  TestStep,,,,4,"Try to switch to another's user:
  # su App2   (App2 is the 2nd user name)",It will fail to switch.,,,,,,,
  TestScript,appfw_neg_app_manifest,AppFW/app,app cannot get assigned to non-existent user,1,Install an application which request multiple groups (eg: bad-groups-app). At least one should be a non-existent group (eg: nonexitent1,nonexistent2),,FVT,ready,IOTOS-418,,,
  TestStep,,,,2,"After system boots up, find the user name of the app under /home/ folder. ",The app user name should be found under /home/ (eg: evil-bad-groups),,,,,,,
  TestStep,,,,3, Command: root# grep SupplementaryGroups /run/systemd/generator/$APPNAME.service, Check that requested non-existent groups (eg: nonexistent1, nonexistent2) are not in the list of assigned groups,,,,,,
  TestScript,test_swupd_remote,Software Update,Full update using swupd,1,use "swupd verify" to make sure current flashed image is in good status for swupdate,no error should be shown in log,FVT,ready,IOTOS-970,,,
  TestStep,,,,2,do repo validation using blackbox tool or other tool at client side, verify repo is correct,repo should be correct,,,,,,
  TestStep,,,,3,apply update task using "swupd_update -v -c" and make sure update complete successfully, this will redownload the update repo,the update should complete successfully and corresponding files are changed,,,,,,
  TestStep,,,,4,do "swupd verify" to check system is correct,check system should be in good status,,,,,,
  
negative.code: TestScript,documentation_REST_APIs,Documentation,To check the docs of REST API,1,Check doc files in https://github.com/01org/iot-rest-api-server/tree/master/doc,See raml files ,FVT,ready,IOTOS-560,,,,
  TestScript,dev_image_workable,OS / Image Configuration,To check dev image is bootable and related packages are inclued,1,Download dev image and install it on P1 platforms to check it can boot successfully,dev image boot successfully,FVT,ready,IOTOS-784,,,,
  TestStep,,,,2,"Check related packages(packagegroup-core-buildessential,smartpm,git,gdb,valgrind) are installed",packages are installed in image,,,,,,,
  TestScript,documentation_How to build/modify Ostro OS,Documentation,To check the Instruction correctness,1,Check the doc mentioned in this Requirement,The doc instruction is correct,FVT,design,IOTOS-835,,,,
  TestScript,documentation_Contributing_to_Ostro_OS,Documentation,To check the Instruction correctness,1,Check the doc mentioned in this Requirement,The doc instruction is correct,FVT,design,IOTOS-836,,,,
  TestScript,documentation_Supported_HW_platforms,Documentation,To check the Instruction correctness,1,make sure platform description is accurate and the links provided are correct,The doc is correct,FVT,ready,IOTOS-837,,,,
  TestScript,sol_oic_find_single_resource,COMMS/Iotivity,Use soletta node type API to find single oic resource,1,"Put 3 test files ('light-client.fbp', 'light-server.fbp' and 'sol-flow.json' from soletta source src/examples/flow/oic/) to IoT device /home/root/ folder. ",,EFT,design,IOTOS-1019,,,,
  TestStep,,,,2,"In the IoT device, it should be able to run fbp file. Then, run:
  