ApexUnit Versions Save

Fixed bug Unable to report for greater than 200 classes (#61). It creates batches of test classes and executes batch by batch. Each batch contains set of 200 classes

addressed few bugs related to

• URL/password encoding (Issue #46)
• code cleanup (Pull request #44)
• updated license headers and readme (#48 and #49 )

Dated: 29th July 2016

Bug fixes: Session renewer support for Issue #11 Code refactoring: Modularized connector config construction for partner Connection and Bulk connection

Leveraging the bug fix: Use src/main/resources/config.properties to set the below parameter: MAX_TIME_OUT_IN_MS(Default value : 1200000 ==> 20 minutes) : Time out setting for the session, Once timeout occurs, session renewer module is invoked which renews the session. Helpful when you face connection exception during query executions.

Related PRs: #38 and #43

Dated: 21st Jan 2016

Bug fixes:

• Apex classes only in the default namespace are considered. In scenarios where there are multiple class names across namespaces, the class in the DEFAULT namespace is selected.

Dated: Jan 08, 2016

Support for proxy connectivity added. This allows for the service to run inside of a specific data center or secured location where direct access to a pod is might be restricted. New CLI Parameters added: -proxy.host : Proxy host for external access -proxy.port : Proxy port for external access

Corresponding pull request: https://github.com/forcedotcom/ApexUnit/pull/15

Date: October 09, 2015

(Base open source version)

ApexUnit 2.x is a powerful continuous delivery tool for Force.com platform and it comprises of two major components:

1. A xUnit based testing framework for Force.com platform;
2. Extensive code coverage metrics with actionable detail for Apex source code. The code coverage results can be a component of the CI/CD pipeline.

Key Features of ApexUnit 2.x:

• Queue and schedule Apex test runs asynchronously
• Filter and group tests(xUnit based)
• Multi-Manifest file and Multi-Regex support for filtering and grouping the tests and sources classes
• Extensive and comprehensive reporting
• Summary of code coverage metrics and test execution with pass/fail rate
• Detailed test report in standard JUnit xml format with drill down feature for failure analysis
• Info on covered and uncovered code lines including line numbers
• Code coverage metrics for individual classes; sorted in ascending order of code coverage%
• Color schemes(red-green) to highlight classes with low code coverage
• Automatic health checks
• Customizable code coverage thresholds at team level and org-wide level
• Halts the tool when code coverage thresholds are not met and/or when there are test failures
• Seamless integration with Jenkins and CD pipeline
• Self-abort long running tests using customizable timeout threshold

Additional features:

• Live test status logging
• Completed test execution count and remaining tests count
• Periodic test status logging
• Test execution time for each test
• Handling and reporting the duplicate/invalid test class name entries in manifest files/regexes
• Man page with details on available command line parameter options (-help)

Please refer README and WIKI pages for the features and How to get started guide.