anchor.diff:  TestStep,,,,2,checkout to different branch to check the git logs,See meta information of different branch,,,,,,,
   TestScript,CI_enable_enabled_security_scan,SCM / Backend Services Configuration,CI system should perform automatically instrumented builds with security scan,1,check tasks enabled in CI,tasks are enabled,FVT,ready,IOTOS-780,,,,
   TestScript,comm_ble_6lowpan_ping,COMMS/Bluetooth,enable 6LowPan over BLE and ping ipv6 address,1,Follow wiki to setup BLE 6LowPan environment.,,FVT,ready,IOTOS-762,,,,
  -TestStep,,,,2,Ubuntu15.04 ping IoT's ipv6 address,"""ping6 -I eth0 <IoT address> -c 1"" PASS",,,,,,,
  -TestScript,comm_ble_6lowpan_ssh,COMMS/Bluetooth,enable 6LowPan over BLE and ssh to ipv6 address,1,Follow wiki to setup BLE 6LowPan environment.,,FVT,ready,IOTOS-762,,,,
  -TestStep,,,,2,Ubuntu15.04 ssh to IoT via its ipv6 address,"""ssh  root@<IoT address>%eth0"" PASS",,,,,,,
  +TestStep,,,,2,One device pings the other's ipv6 address,"""ping6 -I eth0 <IoT address> -c 1"" PASS",,,,,,,
  +TestScript,comm_ble_6lowpan_ssh,COMMS/Bluetooth,enable 6LowPan over BLE and ssh to ipv6 address,1,Follow wiki to setup BLE 6LowPan environment.,,EFT,ready,IOTOS-762,,,,
  +TestStep,,,,2,One device ssh to the other via its ipv6 address,"""ssh  root@<IoT address>%eth0"" PASS",,,,,,,
   TestScript,comm_zigbee_6lowpan_ping,COMMS/Zigbee,enable 6LowPan over ZigBee and ping ipv6 address,1,Follow wiki setup ZigBee 6LowPan environment on two IoT devices (Galileo or Minnowmax),,FVT,ready,"IOTOS-763,IOTOS-1220",,,,
   TestStep,,,,2,One IoT device pings the other's ipv6 address,"""ping6 -I eth0 <IoT address> -c 1"" PASS",,,,,,,
  -TestScript,comm_zigbee_6lowpan_ssh,COMMS/Zigbee,enable 6LowPan over ZigBee and ssh to ipv6 address,1,Follow wiki to setup ZigBee 6LowPan environment on two IoT devices (Galileo or Minnowmax),,FVT,ready,"IOTOS-763,IOTOS-1220",,,,
  +TestScript,comm_zigbee_6lowpan_ssh,COMMS/Zigbee,enable 6LowPan over ZigBee and ssh to ipv6 address,1,Follow wiki to setup ZigBee 6LowPan environment on two IoT devices (Galileo or Minnowmax),,EFT,ready,"IOTOS-763,IOTOS-1220",,,,
   TestStep,,,,2,One IoT device ssh to the other's ipv6 address,"""ssh  root@<IoT address>%eth0"" PASS",,,,,,,
   TestScript,documentation_OIC_JS_API,Documentation,To check the docs of OIC JS API,1,Check spec files ,see md files with API description ,FVT,ready,IOTOS-1178,,,,
   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,,,,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,,,,
  +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,,,,
  +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,,,,
  +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,,,,
  +TestStep,,,,2,Check 'machinectl status iodine-nodetest' to see container information,"Check 'Leader', it should show the correct PID of the app",,,,,,,
  +TestScript,appfw_neg_twoapps_sameuid,AppFW/app,negatively check two application should not use same uid,1,"In ostro-os code, cd meta-appfw/recipes-appfw/. And copy example-app-node to example-app-node1 (modify .bb name to example-app-node1.bb accordingly)",,FVT,design,IOTOS-342,,,,
  +TestStep,,,,2,"In example-app-node1 folder, modify example-app-node1.bb. ","Check 'Leader', it should show the correct PID of the app",,,,,,,
  
positive.code: 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,ready,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,ready,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,ready,IOTOS-1019,,,,
  TestStep,,,,2,"In the IoT device, it should be able to run fbp file. Then, run: 
  > export SOL_MACHINE_ID=""580a3d6a9d194a23b90a24573558d2f4""
  > ./light-server.fbp",The light-server is able to be setup. And no anything output.,,,,,,,
  TestStep,,,,3,"In another terminal, run: ./light-client.fbp","After client running, both client and server part will output continousely:
  LightState true (boolean)
  LightState false (boolean)",,,,,,,
  TestScript,sol_oic_find_multiple_resource,COMMS/Iotivity,Use soletta node type API to scan multiple oic resource,1,Put 2 test files ('light-scan/light-client-scan.fbp' and 'light-scan/sol-flow.json' from soletta source src/examples/flow/oic/) to IoT device /home/root/ folder. ,,EFT,ready,IOTOS-1019,,,,
  TestStep,,,,2,Put light-server.fbp to at least 2 IoT devices. ,,,,,,,,
  TestStep,,,,3,"In the 2 IoT devices, start light-server with different id: 
  > export SOL_MACHINE_ID=""580a3d6a9d194a23b90a24573558d2f4""
  
negative.code: TestScript,ethernet_connect_internet,COMMS/Ethernet,check internet connection via ethernet,1,Ensure ethernet cable is connceted to Internet,,FVT,ready,IOTOS-461,,,,
  TestStep,,,,2,Plug the other port to IoT device,,,,,,,,
  TestStep,,,,3,Check if wget http://www.kernel.org/pub/linux/bluetooth/bluez-5.30.tar.xz,wget command works,,,,,,,
  TestScript,bt_gatt_write_handle,COMMS/Bluetooth,use gatttool to write IoT BLE handle value,1,IoT device does ble advertising. Command is: hciconfig hci0 leadv,,EFT,design,IOTOS-456,,,,
  TestStep,,,,2,"On Host, gatttool -b <iot BT MAC> --characteristics",,,,,,,,
  TestStep,,,,3,"In the characteristics list, use a handle to see its value. Command is: 
  gatttool -b <iot BT MAC> --char-read -a <handle>",,,,,,,,
  