ConcurrentTesting - Advanced Testing for Multi-Threaded Applications

Latest links

Statisticsw

Active Links: 58
Pending Links: 1
Todays Links: 0
Active Articles: 6
Pending Articles: 1
Todays Articles: 0
Total Categories: 33
Sub Categories: 20

ID:	114
Title:	ConcurrentTesting - Advanced Testing for Multi-Threaded Applications
Pagerank:	5
Short Description:	ConTest is a tool that exposes and eliminates concurrency-related bugs in parallel and distributed Java programs. ConTest systematically and transparently schedules the execution of program threads such that program scenarios that are likely to contain race conditions, deadlocks, and other intermittent bugs (collectively called synchronization problems) are forced to appear with high frequency. Because bugs are found earlier in the testing process, ConTest dramatically improves the quality of testing and reduces development expense.  ConTest's impact on the testing effort is minimal. Testers can rerun existing test suites without recompilation of the software under test (but with a greater probability of uncovering synchronization problems). ConTest is easy to use and rcan be set up in less than one day, in most cases. This tool has been used successfully on industrial-sized applications (such as IBM WebSphere) and is, in general, a scalable testing solution. ConTest can also be used to measure test coverage, aid in debugging, and detect potential deadlocks.
Description:	Features are: ConTest is activated by adding a “java_agent” argument to your existing test command and specifying in the ConTest preferences file which of your classes should be targeted. When these classes are loaded by your test, ConTest instruments them around places that are likely to be involved in concurrent bugs. The ConTest run-time engine adds heuristically controlled conditional instructions that force thread switches, thus helping to reveal concurrent bugs. Each existing test can be run many times: ConTest causes different things to happen every time, and new bugs may surface. ConTest also collects run-time information for coverage and debugging. This process requires Java 5 and above. ConTest can work with Java 1.4 as well, but the process is slightly different; please consult the "readme" file.
Category:	Testing
Link Owner:
Date Added:	November 30, 2009 08:35:01 PM
Number Hits:	8
URL:	http://www.alphaworks.ibm.com/tech/contest

RatingsYou must be logged in to leave a rating. Average rating: (0 votes)
Reviews No Reviews Yet. You must be logged in to leave a Comment.

Bookmark Me

Popular Categories

Latest articles

Java Licensing with Agilis
Agilis provides secure, flexible Java protection solutions to software vendors worldwide. Capabilities include Internet-based product activation on connected and disconnected systems, intranet or Internet-based floating licensing, node-locked licensing, named-user licensing, feature configuration, custom licensing, server licensing, trial licensing, subscription licensing, usage-based licensing, licensing via resellers or OEMs, revocable licensing, license reporting, user compliance management, backoffice integration and more.

FireStorm/DAO: What is DAO Design Pattern?
The Data Access Object (DAO) design pattern provides a technique for separating object persistence and data access logic from any particular persistence mechanism or API. There are clear benefits to this approach from an architectural perspective.

CA Plex: what is it?
Today’s business climate requires organizations to have business applications that help improve customer service, reduce costs, increase profits, get to market faster and respond more rapidly to competitive challenges. CA Plex provides a single, integrated environment that enables both traditional and SOA-based solutions for development. CA Plex uses building blocks known as patterns to help your development teams create and maintain large-scale business applications for multiple platforms — Windows/.NET, Java/J2EE or the IBM Power Systems/IBM i.

JCover Code Coverage: important to understand!
Why is coverage analysis important? Coverage analysis has the following benefits: * We can determine if our test suite is adequate. A test suite that achieves 65% statement coverage is hardly adequate. We cannot be confident of our product's quality with this much coverage. This figure prompts us to enhance the test suite. * We can identify redundant test cases that are not useful either in increasing code coverage or in finding new bugs. Fine tuning a test suite has immense benefits during regression testing. * We can find out if there are regions of code that cannot be exercised at all, and hence can be cleaned up. We sometimes find that an application has code to support a feature that was discontinued in an earlier release of the product! Although test cases are normally generated from the specification, coverage analysis helps us in identifying areas that require further test focus.

Codign CoView: JUnit Test Generation
Unit testing and coding go together like peanut butter and jelly. Each good by themself, but together? Now that's a good sandwich! Now you can benefit by easily creating the right JUnit test the first time. CoView provides a solution that makes sense, is unique and completely understandable. And it only takes 3 steps to have a complete set of JUnit tests for each of your classes.

User:		Password:
Keep me logged in.
Register \| I forgot my password

No Reviews Yet.