justforfunc #16: unit testing HTTP servers 

1:42 - Basic Unit Tests 14:27 - Sub tests: 16:12 - Examples as tests 20:03 - Testing HTTP Handlers 39:27 - Testing HTTP routing

One of my favorite things about this series is seeing the collection of stickers grow each video.

Hello, Francesc. Thanks for the video. It helped lot to get into basic testing. Can you please record a video how to mock Handlers dependencies that can be anything like connecting to database or invoking external API's and like so.

I love it! Keep up the good work. As a new programmer working with Go, deep dives into the basics of the language are extremely helpful.

Extremely informative video and still holding its value very well as time goes on. Thank you very much for taking your time to help grow the gophers!

Wasn't expecting to find a video on exactly what I was looking for, but I did. Thanks for the video! One of the live coding videos I've seen.

Excellant video my man. Your channel has been recommended to me, so far, I like your style and topics.

I learned more from this video than any other tutorial on testing that's currently out there. Keep up the good work! Let me know if you have a Patreon account, I would like to donate.

This series is wonderful. I watched it first in 2017 and I come back from time to time. I also use a similar approach to testing and error handling in C now, since my job doesn't allow me to use golang, but it's super effective.

Just a great joy to learn from this series :-) Thanks for providing nice tutorials !

This is really excellent! One tip I discovered just yesterday: if you put "localhost:8080" instead of ":8080" into your ListenAndServe method, it will make that annoying MacOS popup go away (but only after you've run it once)

Been coding in go for 3 years, still picked up some tricks! Great content, thanks!

i miss this series. i wish there was one that was comparable. justforfunc RULES!

Great episode as usual!

Sweet video. Learned a bunch of cool stuff. Really cool example docs thing

I really enjoyed this episode particularly. I have not been writing tests in my code. It was interesting to see how to write tests for network services that I assumed you couldn't easily write tests for. I learned allot.

Awesome episode! I had no idea about this way to test router. Thank you so much for this video. By the way I'm really enjoying to learn Go. It is not only pragmatic and fun but also have an impressive and powerful standard library.

This helped me a lot. Thank you Sir.

Really helpful. Keep up the good work!

thanks been w8ing for this one :)

Great episode. I learnt a lot.

Very good explanation bro , congratulations!

This is sooper cool.. quite informative.. thanks a lot Francesc!!

This is the clearest explanation I've seen, thanks! (or read :) )

Thanks for this hi-quality video!

very good explanations, thank you very much for doing that dude.

thank you for the lesson!

you are too good to be true, but..... YOU ARE REAL !! Thanks for your videos :))

I saw you at Gophercon 2018 in Denver. You had a machine learning talk. I learned that machine learning uses lots of math and is very complicated. I like this channel tho.

Great video!

you are awesome. thank you so much :)

Thanks for this video. A nice compilation of testing 101. I wish you've had made it 12 months ago :) A little note, though: To clean the test code of the webserver a little bit up I would suggest httptest.ResponseRecorder.Body.String(): play.golang.org/p/lga8FW7XKg

Thank you! :D

Hi Francesc, thanks for the great videos, they're really helpful. One thing I don't really get in this one though is the routing part: it seems to me you're testing global server functionalities, not really routing. For example, if in your sample the server was (incorrectly) routing "/double" to a squareHandler() function, you wouldn't see anything wrong since the expected result is 2*2 = 2^2 = 4. To avoid that, you would have to be exhaustive in the tests in TestRouting() but that would create a lot of duplicate code with the handler testing… Is there a simple way to test that a request to a given route is sent to the desired handler? Or what would you think of renaming all handler tests from TestHandler() to testHandler() to make them private, removing all httptest.ResponseRecorder-related code, and call them as sub-tests in the TestRouting() function? Then, `go test` would test every route once with exhaustive tests, and to test only a subset of handlers one could `go test -run Routing/HandlerFoo`, for example.

I like it!

great one and it helped me a lot, thanks , but why your last video is for 5 years ago? where are you?

Hello, Francesc. Thanks a lot for your videos, they are really greate and useful for me as a new gopher. May I to ask you to cover the question about testing more difficult logick inside handlers? Like requests to third-side API's, saving some data in data base and something like that, what happens, then someone makes request to server. Although I find your lessons very cool, more complex examples would be quite good. Thanks again!

excellent!

awesome!!

Why is table based testing the idiomatic way in Go? Is there no way to do test setup / teardown functions to minimise repetition, and this is the alternative? Or is there some other benefit vs. just writing one function per test case like in other programming languages?

thnx so much the best tutorial I am doing my portafolio in one project in golang was very difficult to understand I found many diff ways to do the test but in the end I understand with you examples i hope you still doing more examples tester one question i have how resolve if I need inside of the method to access to database for information for continue my test? from mexico

Thanks Francesc

Awesome

Great Video . Thank you very much!! Very well explained.!! Can you make videos on Sql mocking. Thanks again!

Have you considered testing exception and error cases first, then and only then testing desired cases?

Thanks for great video! I noticed that we used http.NewRequest() and also I found that there is also httptest.NewRequest() that looks more suitable in this case (see stackoverflow.com/questions/45682353/httptest-newrequest-vs-http-newrequest-which-one-to-use-in-tests-and-why). Is there a particular reason why we used the one from http package? Thanks!

I'll try to test my WebSocket game server! (Hope it can be done without mock-everything exercise. :-) )

That was really good. It would be more helpful if you can share how to test client side code which hits an http endpoint and gets a response...

Nice video as usual! Is there any recommendation for naming test within the same pkg and not the same pkg. For example: * sum.go (package sum) * sum_test.go (package sum) * sum_external_test.go (package sumexternal) Or? Any suggestion?

wooohooo

Please do an episode with relational database

How about an episode or two on gRPC and gRPC testing strategies?

Thanks for the video. Any reason why you are using the regular http.NewRequest to create the request for testing instead of the httptest.NewRequest to create the test request?

Have you ever thought about streaming on twitch or something like that? That would be cool for something like a Q&A session or show us projects you're working on.

Hello Francesc, thanks for this vedio.. would you plz share one which covers golang API ( POST ) load testing for performnc bnchmrk with different JSON inputs... Thanks again!

Quan començes a programar en Go i trobes aquest canal... Super ben explicat, thanks!

Why both functions Ints() and Ints() needed? Just Ints() should be sufficient right?

Hi, if we use the t.Run(tc.name, func(t *testing.T) { ...}) for creating subtests and inside the func we have several error condition checks but we want that after the first t.Errorf() is hit, do not follow the current iteration, it shall begin the next one, how could we do this? I've tried using break and continue but do not seems the solution. Should we use in this case t.Fatalf() instead? Best regards

Where did you get the gopher sticker? I want one!

I've got the same EV RE320 mic. What's that XLR-USB interface you're using?

Hello, I have written some unit test cases & an init function to initialize some config variables (reading config from file). But it is breaking because when I run test cases, they call init function then throughs error (file not found). Is there any way to skip the execution of init function while running unit test cases?

How to test methods to consume external API?

Thanks! Although it seems `TestDoubleHandler()` only has downsides vs `TestRouting()` Not sure what to think of it...

Hello, just one question, I am trying to a Handle that also receives a file parameter with the CSV content. I would like to know how I would add this file to the test? I am currently testing my web service like this: curl -F file=@path/matrix.csv "localhost:8080/sum" How could I add the file part to the request in a POST? Thank you!

How would you test functions that execute html-templates?

We like seeing you!!!, but I think it will be better to place your video to a place that do not block any of the code. BTW, keep the good work.

how is he not getting an error for using nil as type int?

Which extension are you using that highlights the coverage on the screen? I can not find it, but really want it!

This package is also pretty handy for testing and mocking HTTP traffic, especially traffic performed by third-party dependencies of your code: github.com/h2non/gock

Hi Francesc, I've tried to create the examples_test.go for my project and everything works fine until I want to generate an example of a method associated to a type. Here is an example, this is the content of my main.go file: type TestType struct{ Name string } func (t *TestType) TestFunc() { fmt.Printf("hello %s", t.Name) } and this is the content of my examples_test.go file: func ExampleTestFunc() { tt := connectors.TestType{Name: "gopher"} tt.TestFunc() // Output: // hello gopher } and when I generate the documentation with godoc there is no mention of the ExampleTestFunc. How could we add examples in this case? P.S. you mention something about goconvey at the beginning of the video but you haven't talk about this tool, will you explain it in the second part of this testing series? Thanks in advance.

R U in Berlin?

TestRouting tests whole flow from input to output then the testDoubleHandler becomes redundant do we still need it @justforfunc

7:16 "2 + 3 is 4..." :)

How do you make the examples runnable in godoc? I've scoured the internet and the standard library for concrete examples with no luck.

When I move the tests into their own pacakge I get the error "Cannot find package 'path/to/package'" in any of: So any ideas on what I need to do?

godoc -http=:6060 -play

How about an episode on crypto

Francesc, do you mind sharing your vscode config, a la github.com/andreis/cfg/tree/master/vscode ? You can list your installed extensions by running `code --list-extensions`