go-bindata
GoConvey
go-bindata | GoConvey | |
---|---|---|
4 | 3 | |
1,798 | 8,108 | |
0.0% | 0.4% | |
0.0 | 5.2 | |
over 2 years ago | 8 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
go-bindata
-
Gokiburi: Automatic Test Runs for Go Projects
BTW, maybe you could consider using the embed or go-bindata packages to embed the UI files in the binary, so it's easier to package/install (either with brew or go install).
-
Разбираем go:embed в Go 1.16
Что если мы хотим встроить файл в наш бинарник на go, например, какие-то шаблоны, html файлы, если это веб сервер или даже README.md ? Нам приходилось либо саморучно затаскивать их в наш код, либо пользоваться сторонними библиотечками, такими как go-bindata. Оба варианта отстойные. Первый способ не гибкий, в нем можно ошибиться, так как нужно все делать вручную. Второй способ получше, но это дополнительные зависимости, которых может не оказаться в вашей среде и главное дополнительные шаги при сборке приложения.
-
Embedding files natively in Go 1.16
Traditionally, we have relied on third-party packages like go-bindata or statik to embed static assets in Go binaries. These tools essentially require to run a command against the assets we want to embed to create a Go file which contains a binary representation of them. Later, you import this generated file in your code and you access the files using some key based on the path or a virtual file system.
- What is the preferred way to package static files (html/css/js) along with your standalone binary in 2020?
GoConvey
-
Gokiburi: Automatic Test Runs for Go Projects
I have always liked to use the similar GoConvey tool for automatic test runs during development, but it has definitely started to “show its age” and since Go 1.20 it hasn’t been able to parse code coverage correctly. So, I decided to dive into making my own tool to replace it for me.
-
Is there a more detailed test coverage report than go test -cover?
IIRC you can use http://goconvey.co/ just for the reports
-
Do you prefer go-convey over golang's t.Run?
For a generic usecase, do you see Go-convey adding any benefit over simple golang t.Run?
What are some alternatives?
go-embed - Generates go code to embed resource files into your library or executable
ginkgo - A Modern Testing Framework for Go
go-resources - Unfancy resources embedding for Go with out of box http.FileSystem support.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
fileb0x - a better customizable tool to embed files in go; also update embedded files remotely without restarting the server
godog - Cucumber for golang
go-bindata - A small utility which generates Go code from any file. Useful for embedding binary data in a Go program.
gomega - Ginkgo's Preferred Matcher Library
gokiburi - Automatic test runs for Go projects
gocheck - Rich testing for the Go language
esc - A simple file embedder for Go
Gauge - Light weight cross-platform test automation