keploy VS pkgsite

October is the month of Open Source and Keploy is taking part in this celebration. You can contribute to several Keploy projects by participating in this year’s Hacktoberfest. You can both contribute to the code part and the no-code part as well. Here are some contributions that you can make!

curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_amd64.tar.gz" | tar xz -C /tmp sudo mkdir -p /usr/local/bin && sudo mv /tmp/keploy /usr/local/bin && keploy

Keploy is an open-source, end-to-end (E2E) testing toolkit for developers. It creates test cases and data mocks/stubs by recording API calls, database queries, etc., making releases faster and more reliable. Keploy works by being added as a middleware to your application. It captures and replays all network interaction served to the application from any source. This allows Keploy to generate test cases for all of your API endpoints, including those that are not explicitly tested by your unit tests. This can help you to identify and fix bugs that would otherwise go undetected. Keploy can create data mocks/stubs for your APIs, which can help you to isolate your tests and make them more reliable. It can automatically compare test cases generated from previously collected traffic against updated behaviour of your application, and bring any differences to your attention. This can help you to identify regressions in your production code early on.

I'm new to SEO, I run an OSS project and Semrush shows my project's main repo link as TOXIC backlink!! I'm not sure if I should add this to the whitelist of my domain.

I have once contributed to one similar project https://github.com/keploy/keploy , This can help you generate e2e tests and mocks as well , with real api and infra calls .

Please feel free to checkout keploy too - https://github.com/keploy/keploy

This looks very similar to keploy but specific to node apps. Keploy is designed to be multi language.

Reading the standard library will give you ideas/insight about various Go idiomatic patterns/approaches, and you can see a full website/API implementation in the pkg.go.dev repository (https://github.com/golang/pkgsite). Projects like https://github.com/etcd-io/etcd may be interesting too.

Let's look at some real codebase for an example on how to write database tests without mocking. The source code for the Go package discovery site(https://pkg.go.dev/) is available at[1] That site uses postgres as its primary database[2]. The database package has a method called GetLatestInfo[3] that fetches the latest versions of a module. That method is called from the frontend http handlers[4] via an interface[5] When it comes to testing that frontend handler, you would expect the tests to use a mock implementation of that interface method. But that's not what they do, instead they use a real postgres database in the test[6].

The code behind pkg.go.dev is also open-source and might be an interesting read.

BTW, the number of dependencies of pkgsite surprises me: https://github.com/golang/pkgsite/blob/master/go.mod

The source for Go's pkg site has been helpful to me https://github.com/golang/pkgsite

In my unpopular opinion, the go net/http is good enough to develop the web http application. The standard API is clean and well-documented. One of example is the pkgsite (https://github.com/golang/pkgsite).

It's also available as a mirror at https://github.com/golang/pkgsite. All the golang.org/x/* packages are thankfully available there, making them pretty easy to find.