A couple of weeks ago, I contributed a patch to net/http/fcgi <https://go-review.googlesource.com/c/40012/> (hooray!). It was simple to develop in this package. I added unit tests for my change and kept running go test inside that package to make sure my change was working. I also routinely ran the main test script - all.bash to make sure testing was exhaustive.
I am now working on another issue <https://github.com/golang/go/issues/18733>. However, when I run go test inside net/http, I get a bunch of errors about golang_org and "use of internal package". This post <http://stackoverflow.com/questions/43702101/golang-core-net-http-package-import-errors> goes into detail on what I'm seeing. I think all.bash includes all unit tests so I could theoretically run that, but that is time consuming. What is a good setup to have when developing in net/http that enables the testing to be done efficiently? Is there an easy way to get rid of the aforementioned errors that would enable only running net/http tests? I am relatively inexperienced so a solution you think is obvious is likely something I haven't tried. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
