JAVA TESTING
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
Checks compliance to configurable sets of over 1000 built-in rules, including out-of the-box support for PCI
DSS,
OWASP Top10, CWE-SANS Top25, and Cigital security static analysis
Corrects violations of 250 rules
Identifiese and prevents threading problems
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
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
Solaris
Linux
Windows System Requirements
Operating System
Windows: Windows 2000, XP, 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)
Apple®/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