Fake VS ginkgo

Fake

We haven't tracked posts mentioning Fake yet.
Tracking mentions began in Dec 2020.

ginkgo

• Mastering Golang Debugging in Emacs
  15 projects | dev.to | 29 Nov 2024

  Debug both standard applications and Ginkgo tests (this is what I'm using at the moment 🤷)

• Go-DOM - 1st major milestone
  2 projects | dev.to | 17 Nov 2024

  Let's explore a simple test, as it looks now in the code base (the code uses Ginkgo and Gomega, a somewhat overlooked combination IMHO)

• Functional Programming in Go
  2 projects | news.ycombinator.com | 8 Nov 2024

  Take a look at the Ginkgo testing framework to see the horrors of shoe horning FP into Go

  https://onsi.github.io/ginkgo/#writing-specs

• Show HN: Gomponents, HTML components in pure Go
  8 projects | news.ycombinator.com | 17 Oct 2024

  It's the same with the Ginkgo testing library: "After the package books_test declaration we import the ginkgo and gomega packages into the test's top-level namespace by performing a . dot-import. Since Ginkgo and Gomega are DSLs this makes the tests more natural to read."

  https://onsi.github.io/ginkgo/

• Leverage Your Test Suite With testcontainers-go & docker-compose
  4 projects | dev.to | 4 Oct 2024

  The ginkgo testing framework helps us in building the test suite. It's entirely written in Go. Furthermore, it provides a CLI utility to set up and run the tests. Since we will use it later, let's download it from here. You can download it in two ways:

• Writing tests for a Kubernetes Operator
  3 projects | dev.to | 7 Oct 2023

  Ginkgo: a testing framework based on the concept of ‌"Behavior Driven Development" (BDD)

• We moved our Cloud operations to a Kubernetes Operator
  3 projects | dev.to | 15 Aug 2023

  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?
  3 projects | /r/golang | 9 Apr 2023

  A bit off-topic, but i really like the ginkgo BDD framework

• Start test names with “should” (2020)
  1 project | news.ycombinator.com | 12 Feb 2023

  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
  2 projects | /r/golang | 17 Jan 2023

  If you are using Ginkgo for your e2e, this library might of help.