You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/01/03 17:04:54 UTC

[GitHub] houshengbo commented on issue #182: Change to use dep tool from golang

houshengbo commented on issue #182: Change to use dep tool from golang
URL: https://github.com/apache/incubator-openwhisk-cli/pull/182#issuecomment-355066311
 
 
   @mcdan First, thanks for contributing to OpenWhisk CLI.
   I believe there is something I need to explain a bit regarding the tests in CLI. By far, we have three type of tests available: unit tests(// +build unit), native tests(// +build native) and integration tests(// +build integration), with the marker on top of each test file.
   Unit test is easy to understand. Native test means it is only able to run after the CLI binary is built and verify the functionalities of the binary without openwhisk services. Integration test means it is only able to run against the openwhisk services after the binary is built and verify the output of the openwhisk services.
   
   IMO, unit tests definitely need to be put next to the file of source code, but for native tests and integration tests, I tend to put them in separate directories for better references. 
   
   When travis launches, we run the unit tests first to verify the source code, then after we build the binary, we run the native tests to check whether the binary is built with the expected behaviors. Finally, we deploy openwhisk service, and run the integration tests to make sure we receive the expected results from openwhisk and process them correctly in CLI binary.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services