Include tests in binary and run them

[farid.m...@gmail.com]

We've written some diagnostic tests that we execute during the test phase (go test) however I was wondering if there's an established

pattern for how to include tests in the final binary and execute them afterwards.

The analogous version in Java would be that you could create a "test JAR" which contains the test classes and execute an XUnit framework (JUnit) programmatically yourself run the tests.

[Dan Kortschak]

You can ask go test to leave the test executable for you to use later.
This is done with the -c flag. It will leave a <package>-test binary
that takes all the flags that go test takes. This is at least similar
to what you are asking for.

[Farid Zakaria]

That's not bad and good to know. 

Thanks for sharing !

Fundamentally I want to include the tests in the main though executable and then run testing.T myself in the normal main

(Through a CLI command)

I'm willing to accept it can't be done because ts not idiomatic but thought I'd inquire. 

[Marko Ristin-Kaufmann]

Hi Farid,

If I understood your question correctly, you can play with build flags. Alternatively, you can add a "-diagnostics" flag.

Consider also design-by-contract with contracts tested at run time (e.g., we use our own implementation https://github.com/Parquery/gocontracts; see also other implementations in the readme).

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1441787d-eb2b-479e-821c-934694fbe6b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sean Liao]

I think testing.MainStart() does what you want though do nore the caveats

https://golang.org/pkg/testing/#MainStart

[Sean Liao]

actually looking into it more since *_test,go files aren't included in a normal build you are probably better off just writing your tests as normal functions if you want them included in the final build

[Tamás Gulácsi]

2019. július 10., szerda 6:43:39 UTC+2 időpontban Farid Zakaria a következőt írta:

That's not bad and good to know. 

Thanks for sharing !

Fundamentally I want to include the tests in the main though executable and then run testing.T myself in the normal main

(Through a CLI command)

I'm willing to accept it can't be done because ts not idiomatic but thought I'd inquire. 

On Tue, Jul 9, 2019, 9:40 PM Dan Kortschak <d...@kortschak.io> wrote:

You can ask go test to leave the test executable for you to use later.
This is done with the -c flag. It will leave a <package>-test binary
that takes all the flags that go test takes. This is at least similar
to what you are asking for.

On Tue, 2019-07-09 at 18:35 -0700, farid....@gmail.com wrote:
> We've written some diagnostic tests that we execute during the test
> phase
> (go test) however I was wondering if there's an established
> pattern for how to include tests in the final binary and execute
> them
> afterwards.
>
> The analogous version in Java would be that you could create a "test
> JAR"
> which contains the test classes and execute an XUnit framework
> (JUnit)
> programmatically yourself run the tests.
>

go test -c

and append yourpacakge.test onto yourpackage binary as a zip file with github.com/GeertJohan/go.rice/rice .