Search Results for "work"

Toxiproxy is a framework for simulating network conditions. It's made specifically to work in testing, CI and development environments, supporting deterministic tampering with connections, but with support for randomized chaos and customization. Toxiproxy is the tool you need to prove with tests that your application doesn't have single points of failure. We've been successfully using it in all development and test environments at Shopify since October, 2014.

Terratest is a Go library that provides patterns and helper functions for testing infrastructure, with 1st-class support for Terraform, Packer, Docker, Kubernetes, AWS, GCP, and more. Create a file ending in _test.go and run tests with the go test command. E.g., go test my_test.go. Use Terratest to execute your real IaC tools (e.g., Terraform, Packer, etc.) to deploy real infrastructure (e.g., servers) in a real environment (e.g., AWS). Use the tools built into Terratest to validate that the...

Go to "Files" to download releases of EZComm and Jirrit. EZComm (EZ Comm) is still maintened, code hosted on https://github.com/bon-ami/ezcomm You can use it as either a client or a server for TCP/UDP text messages Jirrit is still maintened, code hosted on https://github.com/bon-ami/jirrit You can use it to operate with commands on JIRA, bugzilla, Jenkins and Gerrit. EZOutput is hosted on https://gitee.com/bon-ami/ezoutput

Static Application Security Testing (SAST) engine focused on covering the OWASP Top 10, to make source code analysis to find vulnerabilities right in the source code, focused on agile and easy-to-implement software inside your DevOps pipeline. Support the following technologies: Java (Maven and Android), Kotlin (Android), Swift (iOS), .NET. Insider is focused on covering the OWASP Top 10, to make source code analysis to find vulnerabilities right in the source code, focused on a agile and...

...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.