Radargun is a framework that benchmarks various Java based caching/data grid products (open source and commercial) against each other. The goal is that end users configure the test framework based on their own cache usage needs so comparisons are extremely relevant. even though it was primarily intended for benchmarking distributed caches/data grids, it can also be used for comparing local caches (e.g. JSR107). Radargun has been successfully used for benchmarking performance under heavy load on 100+ nodes clusters.
(Link: radargun – benchmark java datagrids)
Archive | testing RSS feed for this section
radargun – benchmark java datagrids
December 20, 2010
0 Comments
My life as a Code Economist
December 19, 2010
0 Comments
So why would an ISV ever intentionally release a product with known bugs? Several reasons:
You release with known bugs because you care about quality so deeply that you know how to decide which bugs are acceptable and which ones are not.You release with known bugs because it is better to ship a product with a quality level that is known than to ship a product which is full of surprises waiting to happen.You release with bugs because the alternative is to fix them and risk introducing more bugs which are worse than the ones you have now.All of the reasons for such a decision are tied up in this one basic truth:
Every time you fix a bug, you risk introducing another one.
(Link: My life as a Code Economist)
Cuke4Ninja: The Secret Ninja Cucumber Scrolls | Behaviour Driven Development
September 23, 2010
0 Comments
This document is a step-by-step guide for Cucumber, a tool that is quickly becoming the weapon of choice for many agile teams when it comes to functional test automation, creating executable specifications and building a living documentation.
(Link: Cuke4Ninja: The Secret Ninja Cucumber Scrolls | Behaviour Driven Development)
Hydra – Spread your tests over processors and/or multiple machines to test your code faster.
September 11, 2010
0 Comments
Hydra is a distributed testing framework. It allows you to distribute your tests locally across multiple cores and processors, as well as run your tests remotely over SSH.
Hydra’s goals are to make distributed testing easy. So as long as you can ssh into a computer and run the tests, you can automate the distribution with Hydra.
(Link: Hydra – Spread your tests over processors and/or multiple machines to test your code faster.)
Shoulda – Making tests easy on the fingers and eyes
September 11, 2010
0 Comments
Shoulda makes it easy to write elegant, understandable, and maintainable tests. Shoulda consists of matchers, test helpers, and assertions. It’s fully compatible with your existing tests in Test::Unit or RSpec, and requires no retooling to use.
(Link: Shoulda – Making tests easy on the fingers and eyes)
Grease Your Suite – Tips and Tricks for faster testing
September 11, 2010
0 Comments
ab – Apache HTTP server benchmarking tool – Apache HTTP Server
September 11, 2010
0 Comments
ab is a tool for benchmarking your Apache Hypertext Transfer Protocol (HTTP) server. It is designed to give you an impression of how your current Apache installation performs. This especially shows you how many requests per second your Apache installation is capable of serving.
(Link: ab – Apache HTTP server benchmarking tool – Apache HTTP Server)
Google Page Speed Home
September 11, 2010
0 Comments
Page Speed is an open-source Firefox/Firebug Add-on. Webmasters and web developers can use Page Speed to evaluate the performance of their web pages and to get suggestions on how to improve them.
(Link: Google Page Speed Home)
WebPagetest – SAAS Yslow
September 11, 2010
0 Comments
runs yslow in a friendly way
(Link: WebPagetest – SAAS Yslow)
InfoQ: Testing is Overrated
July 22, 2010
0 Comments
Developer-driven testing is probably the most influential software development technique of the last 10-15 years. There’s no question that it has improved the practice of building software. And in a dynamic language like Ruby, it’s hard to get by without it. But is it really the best way to find defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
(Link: InfoQ: Testing is Overrated)
