Parasoft Logo ChinaJapan
Parasoft delivers quality as continous process
Home My Parasoft Forum Technical Support Live Support Contact
Search Search
User Name:
Password:
[Log In] [Sign Up]
My Parasoft
Solutions
Technologies
Products
Evaluation Request
Resources
Partners
Newsroom
Company
SOAtest
Jtest
C++test
Insure++
ADP Book
  Home > Products > Jtest
Parasoft Jtest®
Provides fast and easy ways to apply a comprehensive set of Java best practices. Automatically builds a robust regression test suite that identifies defects immediately upon introduction and determines if code modifications break existing functionality.

To learn more about Jtest software solution options, call our experts at 888-305-0041 (x-3501) or see more details below.
 White Papers & Presentations:
> White Papers / Product Info
> Product Demo
> Product Presentation
> Webcasts - Lehman Bros., Transcore, others
> Case Studies
 Software Downloads:
Customers and Evaluators, submit your contact information here, and a Parasoft representative will contact you promptly.

Jtest Product Overview

Parasoft Jtest is a comprehensive Java testing product for development teams building Java EE, SOA, Web, and other Java applications. Whether a team is trying to build quality into new code or extend a legacy code base without breaking existing functionality, Jtest provides them a practical way to ensure that their Java code works as expected. It empowers them to modify their code quickly and with confidence, resulting in optimization of development resources and control of development schedules and costs.

Jtest is packaged and licensed in the following editions designed to separate functionality to specific roles and processes in the typical software development environment:

  • Jtest Professional Edition
  • Jtest Architect Edition
  • Jtest Server Edition

Edition details are described in Jtest Editions and Licenses.

HERE’S WHAT OUR CUSTOMERS SAY:
Giorgio Frondoni, Software Manager, Transcore – “Jtest allows us to reduce errors at the source, adjust our practices as necessary to eliminate a repeat of that error, and improve our overall software development process that carries forward from project to project. That is where we save real time and money in the long run.”

To learn more about Jtest, see:

   

Benefits

  • Modify existing code quickly, and with confidence — Enables teams to quickly build a regression safety net that will expose defects immediately upon introduction and determine if code modifications break existing functionality— even if the team has a large existing code base with no tests or minimal tests.
  • Control development costs and schedules — Exposes errors as early as possible, which is when they are fastest and cheapest to fix. Tests a broad range of potential user paths to uncover difficult-to-find problems that could delay releases or require post-release patches.
  • Optimize development resources — Automatically vets approximately 80% of coding issues so developers can spend less time on line-by-line inspections and debugging, and more time on design, algorithms, and implementation.
  • Leverage the power of the latest technologies while controlling their risks — Reduces the difficulty of testing complex enterprise applications (such as SOA/Web services and Java EE applications).
  • Gain instant visibility into Java code's quality and readiness — Provides on-demand objective code assessments and tracks progress towards quality and schedule targets.

Features

  • Automatically creates sensitive low-noise regression test suites—even for large code bases
  • Automatically finds runtime bugs in execution paths that may cross multiple methods, classes, or packages
  • Generates functional JUnit test cases that capture actual code behavior as a deployed application is exercised
  • Generates extendable JUnit and Cactus (in-container) tests that expose reliability problems and capture behavior
  • Executes the test suite to identify regressions and unexpected side effects
  • Parameterizes test cases for use with varied, controlled test input values (runtime-generated, user-defined, or from data sources)
  • Monitors test coverage and achieves high coverage using branch coverage analysis
  • Identifies memory leaks during test execution
  • Steps through tests with the debugger
  • Tests individual methods, classes, or large, complex applications
  • Checks compliance to configurable sets of over 700 built-in rules, including 100 security rules
  • Corrects violations of 250 rules
  • Allows creation of custom rules by modifying parameters, using a graphical design tool, or providing code that demonstrates a sample rule violation
  • Calculates metrics such as Inheritance Depth, Lack Of Cohesion, Cyclomatic Complexity, Nested Blocks Depth, Number Of Children
  • Identifies and refactors duplicate and unused code
  • Supports Struts, Spring, Hibernate, EJBs, JSPs, servlets, and so on
  • Full integration with Eclipse, RAD, JBuilder
  • Limited integration (result import only) with IntelliJ IDEA and Oracle JDeveloper
  • Integration with most popular source control systems
  • Automates the peer code review process (including preparations, notifications, and routing)
  • Shares test settings and files team-wide or organization-wide
  • Generates HTML and XML reports
  • Tracks how test results and code quality change over time
  • Provides GUI (interactive) and command-line (batch) mode

Platforms

  • Windows 2000, Windows XP, Windows 2003 Server, Windows Vista
  • Solaris
  • Linux
  • Mac OS X

Window System Requirements

Operating System

  • Windows 2000, XP, 2003, or Vista

IDE (for plugin version only – not required for standalone version)

  • Eclipse 3.4-3.0, IBM Rational Application Developer 7.0-6.0, JBuilder 2007

Hardware

  • Intel Pentium III 1.0 GHZ minimum; Intel® Pentium IV Single Core 3.0 GHZ recommended
  • SVGA 800x600 display minimum; 1280x1024 recommended
  • 1 GB RAM minimum; 2 GB RAM recommended
  • A mouse or an alternative pointing device

JRE

  • Sun Microsystems JRE 1.3 or higher (32-bit)

Linux/Solaris System Requirements

Operating System

  • Linux: Red Hat Enterprise Linux 3, 4, 5 (glibc version 2.3.2 or higher, package compat-libstdc++-33 installed)
  • Solaris: Solaris 8, 9, or 10
  • Windowing system: Motif xServer or OpenWin (Solaris) or GTK (Linux)

IDE (for plugin version only – not required for standalone version)

  • Eclipse 3.4-3.0, IBM Rational Application Developer 7.0-6.0, JBuilder 2007

Hardware

  • Linux: Intel® Pentium® III 1.0 GHZ minimum; Intel Core 2 Duo 2.0 GHz or higher recommended
  • Solaris: UltraSPARC processor 1.0 GHZ minimum; 2 UltraSPARC processors 1.5 GHz or higher recommended
  • SVGA (800x600) display minimum; 1280 x 1024 or higher recommended
  • 1 GB RAM minimum; 2 GB RAM recommended
  • A mouse or an alternative pointing device

JRE

  • Sun Microsystems JRE 1.3 or higher (32-bit)

Mac System Requirements

Operating System

  • Mac OS X 10.5 or higher

IDE

  • Eclipse 3.2, 3.3, or 3.4

Hardware

  • Intel® Xeon® 2.0 GHz or higher recommended
  • SVGA (800x600) display minimum (1024 x 768 recommended)
  • 1 GB RAM minimum; 2 GB RAM recommended
  • A mouse or an alternative pointing device
Copyright © 1996-2008 Parasoft   T: 888-305-0041   E: info@parasoft.com