Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 2

Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance. Apache JMeter may be used to test performance both on static and dynamic resources (files, Servlets, Perl scripts, Java Objects, Data Bases and Queries, FTP Servers and more). It ... [More] can be used to simulate a heavy load on a server, network or object to test its strength or to analyze overall performance under different load types. You can use it to make a graphical analysis of performance or to test your server/script/object behavior under heavy concurrent load. [Less]

4.03846
   
  2 reviews  |  150 users  |  190,847 lines of code  |  3 current contributors  |  Analyzed 7 days ago
 
 

The Grinder is a load testing framework that makes it easy to run a distributed test using many load injector machines. Test scripts are written in Jython, and can call out to arbitrary Java code, providing support for testing a large range of network protocols. The Grinder comes with a mature ... [More] plug-in for testing HTTP services, HTTP scripts can be recorded easily from a browser session. [Less]

4.0
   
  0 reviews  |  45 users  |  96,806 lines of code  |  3 current contributors  |  Analyzed about 24 hours ago
 
 

boomerang is a piece of javascript that measures your page performance from the end user's perspective. It can measure page load time, bandwidth, latency and more.

5.0
 
  0 reviews  |  5 users  |  7,182 lines of code  |  2 current contributors  |  Analyzed 2 days ago
 
 

Bringing the awesomeness of The Grinder to the .Net community. Bringing the awesomeness of the .Net programming languages to the Grinder community. GrinderScript.Net is an open source project, that enables you to run load test written in a .Net language in The Grinder. It is not a port of The Grinder to the .Net platform.

0
 
  0 reviews  |  1 user  |  10,586 lines of code  |  1 current contributor  |  Analyzed 7 days ago
 
 

This project aims to improve JMeter's reports presentation of a performance tests execution for a better and easier analysis of the results.

0
 
  0 reviews  |  1 user  |  701 lines of code  |  0 current contributors  |  Analyzed 6 days ago
 
 

IxoraRMS is a tool for visualizing monitoring data. It is written in Java and has a Swing GUI. As part of my job I am involved in performance testing and I felt the need for a tool with the following characteristics: quick to deploy able to provide rich amounts of monitoring data able to ... [More] automatically update the customized data views when the topology changes and able to customize the following aspects by writing none or very little code: adding new monitoring agents data visualization adding complex reactions to trigger notifications and tuning/configuration advices Visit ixorarms.com for more information. [Less]

0
 
  0 reviews  |  0 users  |  174,861 lines of code  |  0 current contributors  |  Analyzed 4 days ago
 
 

IxoraRMS is an open source monitoring tool with great visualization and customization capabilities. It is well suited for use in performance labs.

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

Metatrace is a C++ compile time ray tracer (as of the initial release, it is a whitted style one). It is mostly inane stuff. except, maybe, that it's a nice gadget to test compiler performance and conformance, especially but not exclusively in the Template and Metaprogramming corner of C++. ... [More] It requires basic C++-0x support. To use g++, have at least version 4.4 installed. [Less]

0
 
  0 reviews  |  0 users  |  1,088 lines of code  |  0 current contributors  |  Analyzed 3 days ago
 
 

Remember JUnitPerf? If you do, you may find these extensions useful. These extensions were built to bring something similar to JUnitPerf into the JUnit 4.5 framework. These extensions provide the following: a different approach for ignoring tests: any test that doesn't meet a ... [More] programmatically defined condition won't be executed. The evaluation of a condition occurs at runtime. Remember the @Ignored annotation? Well, this is its runtime-equivalent. a way (still experimental) for integrating Guice into our tests. a way for defining performance tests from existing tests in a Xml file. Let's see some examples.... Using the @If annotation @RunWith(ConditionalJUnitClassRunner.class) public static class TestX { @Test @If(condition = "isDBConnectionOk", callee = ConditionHolder.class) public void testOne() throws Exception { //some assertions will go here. } @Test @If(condition = "isDBConnectionOk") public void testTwo() throws Exception { //some assertions will go here. } public static boolean isDBConnectionOk(){ // ... check connect return true; } // some class that contains some functionality that will indicate // which tests to run. public static class ConditionHolder { public ConditionHolder(){} public boolean isDBConnectionOk(){ // ... check connect return true; } } } II. Bootstrapping ala Guice @RunWith(ConditionalJUnitPerfClassRunner.class) @BootstrapWith(ModuleClass.class) class BootstrappingTest { @Inject Unknown member; @Inject Member unknown; @Test @If(condition = "isDBConnectionOk") public void testSomething() throws Exception { Assert.assertTrue(member.recognize(unknown)); } @Test @If(condition = "isDBConnectionOk") public void testSomethingElse() throws Exception { Assert.assertTrue(member.recognize(unknown)); } public static boolean isDBConnectionOk(){ // ... check connect return true; } public static class ModuleClass implements Module { public void configure(Binder binder){ binder.bind(Unknown.class).to(UnknownImpl.class); binder.bind(Member.class).to(MemberImpl.class); } } } III. Performance tests a la Xml @RunWith(PerformanceSuite.class) @ConfigureWith("test.xml") public static class A { @Test public void testNumberOfTestsToRun() throws Exception { //some assertions will go here. } } ... and where is my test.xml? <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> com.gotobject.junit.ClassRunnerExtensionsTest.SimpleTestXml But, what if I don't want to define my performance tests in a Xml file? Well, you can use my ConditionalJUnitPerfClassRunner in conjunction with three performance test's annotations: @Load, @Response, and @Throughput. @RunWith(ConditionalJUnitPerfClassRunner.class) public static class ExplicitlyDefinedPerformanceTest { @Load("feedMePlease") @Test public void testNumberOfTestsToRun() throws Exception { //some assertions will go here. } @Response("feedMePlease") @Test(timeout = 70000L) @If(condition = "isDBConnectionOk") public void testSomethingToo() throws Exception { //some assertions will go here. } @Throughput("feedMePlease") @Test(timeout = 70000L) public void testRealStuff() throws Exception { //some assertions will go here. } @ConfigureWith public static Object[][] feedMePlease(){ return new Object[][]{ new Object[]{ 1, // users 20 // iterations } }; } public static boolean isDBConnectionOk(){ // ... check connect return true; } } These extensions are still under development. This is only version 0.2. There is still more work to do. However, this is not roadblock for you. So go ahead and use them :-). Thanks. [Less]

0
 
  0 reviews  |  0 users  |  46,938 lines of code  |  0 current contributors  |  Analyzed 3 days ago
 
 

A Web Service Composition Generator

0
 
  0 reviews  |  0 users  |  2,772 lines of code  |  2 current contributors  |  Analyzed 5 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.