Beaker is a Puppet testing harness focused on acceptance testing via interactions between multiple (virtual) machines. It provides platform abstraction between different Systems Under Test (SUTs), and it can also be used as a virtual machine provisioner setting up machines, running any commands on those machines, and then exiting. Recently, Vox Pupuli, a collective of Puppet community authors, has taken over responsibility to care and feed Beaker for its continued widespread community use.

In most cases, when users start to access and use a new application or a new release, app performs pretty well. As the user base grows and usage increases, the app can outgrow its infrastructure. Users can start experiencing a dip in performance. Latency increases, bandwidth and memory get exhausted quickly, and some code architectures start to fail because they do not scale well with the increased amount of users.

Apache JMeter is an open source tool for load testing Java applications in both development and CI environments in order to ensure that sudden spikes in traffic won’t cause latency in production. But because load testing involves sending thousands of requests per minute in order to simulate real traffic, it can be difficult to parse outcomes and read patterns—especially for large organizations that test and deploy new code several times a day.

In software development, processing and storing data in different states reflects the business rules an application is built on. The heart and soul of any software application is the data that is persisted in databases for retrieval and further processing. The database system (SQL or Non-SQL) chosen for an application must serve the required data processing and storage needs of the application.

Speedscale was built primarily to provide engineering teams with better insight into their applications over time, replaying single transactions for root cause analysis that give developers and SREs confidence that tomorrow’s application code will work just as well in production as it did yesterday.

SQL injection is one of the most destructive ways an application can be attacked. This kind of attack is targeted toward the application database, which can result in consequences that are irreversible, lead to loss of money, and reduce user trust in your company. There are far too many application data breaches happening every day, usually when a malicious agent attacks the database.

To transform their application delivery, many teams are employing model-based testing (MBT). Through this increasingly popular approach, teams are realizing a number of significant benefits, including improving test coverage, reducing testing effort, and improving quality. In this blog, I’ll examine the use of MBT, but with a particular focus on some of the objectives we often hear DevOps teams say they’re focused on.

Testing in production simply means testing new code changes in production, with live traffic, in order to test the system’s reliability, resiliency, and stability. It helps teams solve bugs and other issues faster, as well as effectively analyze the performance of newly released changes. Its overall purpose is to expose problems that can’t be identified in non-production environments for reasons that may include not being able to mimic the concurrency, load, or user behavior.