When pulling/using the template with the $ faas-cli the only content the user will see is the function folder.
Generally, a relevant topic is how to test within a FaaS applications/code base. Therefore I would recommend the shipping of a minimal test setup. This could consist of a test folder containing tests ensuring the correct implementation of the FaaS (usage of CB). In addition, we would need a .dockerignore containing the test folder, this should ensure that no tests will be in the build image. Any thoughts on the Idea?
When pulling/using the template with the
$ faas-clithe only content the user will see is the function folder.Generally, a relevant topic is how to test within a FaaS applications/code base. Therefore I would recommend the shipping of a minimal test setup. This could consist of a
testfolder containing tests ensuring the correct implementation of the FaaS (usage of CB). In addition, we would need a.dockerignorecontaining thetestfolder, this should ensure that no tests will be in the build image. Any thoughts on the Idea?