ginkgo
httprouter
Our great sponsors
ginkgo | httprouter | |
---|---|---|
13 | 37 | |
7,911 | 16,263 | |
- | - | |
8.8 | 5.3 | |
4 days ago | 23 days ago | |
Go | Go | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ginkgo
-
Writing tests for a Kubernetes Operator
Ginkgo: a testing framework based on the concept of "Behavior Driven Development" (BDD)
-
We moved our Cloud operations to a Kubernetes Operator
We were also able to leverage Ginkgo's parallel testing runtime to run our integration tests on multiple concurrent processes. This provided multiple benefits: we could run our entire integration test suite in under 10 minutes and also reuse the same suite to load test the operator in a production-like environment. Using these tests, we were able to identify hot spots in the code that needed further optimization and experimented with ways to save API calls to ease the load on our own Kubernetes API server while also staying under various AWS rate limits. It was only after running these tests over and over again that I felt confident enough to deploy the operator to our dev and prod clusters.
-
Recommendations for Learning Test-Driven Development (TDD) in Go?
A bit off-topic, but i really like the ginkgo BDD framework
-
Start test names with “should” (2020)
You obviously are not familiar with the third circle of golang continuous integration hell that is ginkgo+gomega:
https://onsi.github.io/ginkgo/#adding-specs-to-a-suite
It’s actually worse than that example suggests. Stuff like Expect(“type safety”).ShouldBe(GreaterThan(13)) throws runtime errors.
The semantics of parallel test runs weren’t defined anywhere the last time I checked.
Anyway, you’ll be thinking back fondly to the days of TestShouldReplaceChildrenWhenUpdatingInstance because now you need to write nested function calls like:
Context(“instances”, func …)
Describe(“that are being updated”, …)
Expect(“should replace children”, …)
And to invoke that from the command line, you need to write a regex against whatever undocumented and unprinted string it internally concatenates together to uniquely describe the test.
Also, they dump color codes to stdout without checking that they are writing to a terminal, so there will be line noise all over whatever automated test logs you produce, or if you pipe stdout to a file.
-
ginkgo integration with jira/elasticsearch/webex/slack
If you are using Ginkgo for your e2e, this library might of help.
-
Testing frameworks, which to use?
https://onsi.github.io/ginkgo/ offers a simple way to create tables with different scenarios useful to generate different test cases based on a file like a yml without to need to develop useless code. Maybe at start seems to be a little verbose but depends how you design the test case.
-
Testza - A modern test framework with pretty output
What are people’s thoughts on testing frameworks? I’ve heard that most devs only use the testing package in the standard library and the testify package for assertions— I assume this is because Go is meant to be lightweight and scalable, and adding external dependencies basically goes against that. But I’ve also seen devs use packages like ginkgo to make tests more structured and readable. What do you guys think?
-
What are your favorite packages to use?
Ginkgo Behavioural test framework
-
Air – Live reload when developing with Go
If you write your tests with Ginkgo [0] its CLI can do this for you. It also has nice facilities to quickly disable a test or portion of a test by pretending an X to the test function name, or to focus a test (only run that test) by prepending an F. It’s pretty nice.
[0]: https://onsi.github.io/ginkgo/
-
Half a million lines of Go at The Khan Academy
The BDD testing framework Ginko [1] has some "weird" / unidiomatic patterns, yet it is very popular
https://github.com/onsi/ginkgo
httprouter
-
Authentication system using Golang and Sveltekit - Initialization and setup
Following the completion of the series — Secure and performant full-stack authentication system using rust (actix-web) and sveltekit and Secure and performant full-stack authentication system using Python (Django) and SvelteKit — I felt I should keep the streak by building an equivalent system in PURE go with very minimal external dependencies. We won't use any fancy web framework apart from httprouter and other basic dependencies including a database driver (pq), and redis client. As usual, we'll be using SvelteKit at the front end, favouring JSDoc instead of TypeScript. The combination is ecstatic!
-
Gin - HTTP web framework written in GO.
Gin is a web framework written in Go. It features a martini-like API with performance that is up to 40 times faster thanks to httprouter. If you need performance and good productivity, you will love Gin.
-
what's your recommended router? chi, mux, something else?
But, if you care about speed take a look at httprouter. That's the one we're using in our company. It's fast but the biggest downsides for me are:
-
go-mir - a toolkit to develop RESTful API backend service like develop service of gRPC
Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
shift: high-performance HTTP router for Go
Also, you seemed to have copied the path.go from Julien Schmidt's httprouter without even thanking or mentioning it in the README, which I think is not a good attitude. Yes, httprouter is BSD-3-Clause licensed, but showing the people that you took the code from some respect, should be a absolute must, in my opinon.
-
What mux/router to use now a days?
For a simple web app, https://github.com/julienschmidt/httprouter
-
Luciano Remes | Golang is 𝘼𝙡𝙢𝙤𝙨𝙩 Perfect
Take this as the high-performing router (I used this in an early demo for the company I worked for when we considered Golang). https://github.com/julienschmidt/httprouter/blob/34250257ea144905c752bfaae80d6885f190daf6/tree.go
-
Implemented a bench marker to compare Go's HTTP Router
The julienschmidt/go-http-routing-benchmark is the julienschmidt/httprouter, but maintenance seemed to have stopped in recent years, so I decided to create my own benchmarker and implement it. I decided to implement bench markers.
-
Standard library, Fiber, Iris, Gin, ... where does one even begin with writing production web apps in Go?
As another aside, I will actively discourage Iris. https://github.com/julienschmidt/httprouter/issues/148 https://www.reddit.com/r/golang/comments/b481q7/a_warning_about_githubcomkatarasiris/
What are some alternatives?
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
chi - lightweight, idiomatic and composable router for building Go HTTP services
godog - Cucumber for golang
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
goblin - Minimal and Beautiful Go testing framework
Echo - High performance, minimalist Go web framework
httpexpect - End-to-end HTTP and REST API testing for Go.
fasthttp - Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http
gocheck - Rich testing for the Go language
Fiber - ⚡️ Express inspired web framework written in Go