Search Results for "up to"

...Over time the team gained a solid foundation of the grammar of the language so we could then start to build systems. This is for people who are interested in picking up Go and/or people who already know some Go, but want to explore testing more.

...A TCP proxy written in Go (what this repository contains) and a client communicating with the proxy over HTTP. You configure your application to make all test connections go through Toxiproxy and can then manipulate their health via HTTP. See Usage below on how to set up your project.

Ginkgo is a Go testing framework built to help you efficiently write expressive and comprehensive tests using Behavior-Driven Development (“BDD”) style. It is best paired with the Gomega matcher library but is designed to be matcher-agnostic. These docs are written assuming you’ll be using Gomega with Ginkgo. They also assume you know your way around Go and have a good mental model for how Go organizes packages under $GOPATH. Ginkgo is tested against Go v1.6 and newer To install Go, follow...

...GoReplay is an innovative open source tool that captures and replays live HTTP traffic, using it to continuously test your system with real data. Now you don’t have to put up with risks that come with putting a third-party component in the critical path. With GoReplay you can analyze and record your application traffic without affecting it whatsoever. Use it for shadowing, load testing, monitoring and detailed analysis. You can trust GoReplay to accurately emulate production environments so you can make changes and deploy with confidence.

...Or maybe you've written a monitoring framework which is capable of gathering a bunch of metrics, then evaluating a few expressions to see if any metrics should be alerted upon, but the conditions for alerting are different for each monitor. A lot of people wind up writing their own half-baked style of evaluation language that fits their needs but isn't complete. Or they wind up baking the expression into the actual executable, even if they know it's subject to change. These strategies may work, but they take time to implement, time for users to learn, and induce technical debt as requirements change.