Exclude fake components from build process

[danielsuguimoto]

As discussed with the team, we don't need to compile the fake components, which are used only for testing, into the final binary files

[fabriciojs]

Another idea, other than build tag conditionals, we could suffix files with _test, not sure about any possible downsides.

[danielsuguimoto]

@fabriciojs build tags won't work at all, because the fake structs and interface are under the same package of the real ones, so the compiler understand that they must be available to entire package, so you cannot ignore them on building process. But we could use build tags if we put all tests and fakers in separated packages, keeping in the original packages only the code that will be built.

[danielsuguimoto]

Another idea, other than build tag conditionals, we could suffix files with _test, not sure about any possible downsides.

I'm not sure, but I guess that unnecessary code will be executed on our tests, if golang executes any function inside *_test.go files as test cases...

[fabriciojs]

The functions executed should be only t ones prefixed with test. Now about the build tags - you are saying we cannot ignore only one file from one package? I didn’t get that but will follow up on research about it.

…

On Tue, 12 Jan 2021 at 17:20 Daniel Jun Suguimoto ***@***.***> wrote: Another idea, other than build tag conditionals, we could suffix files with _test, not sure about any possible downsides. I'm not sure, but I guess that unnecessary code will be executed on our tests, if golang executes any function inside *_test.go files as test cases... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#224 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIQRWJ4K2CRKJSAJMTRGYTSZSVJTANCNFSM4U424KHQ> .

[fabriciojs]

This is not something pressing, nor causing any noticeable downsides. Can we close this?

[danielsuguimoto]

@fabriciojs yep, for me it's ok closing it...