[LANG-1409] Crashes when testing StringUtils and CharSequenceUtils

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.7
• Component/s: lang.*
• Labels: test

Environment

Ubuntu 16.04.4 LTS, and McOs High Sierra-10.13.5
Junit-4.12

• Assignee: Unassigned
• Reporter: Mozhan Soltani
• Created: 09/Aug/18 20:47
• Updated: 28/Dec/20 08:13

Description

The attached test suites for org.apache.commons.lang3.StringUtils.java and org.apache.commons.lang3.CharSequenceUtils.java come from a prototype I have been working on which combines static analysis and automated test generation.

The prototype analyses a specified dependency of a project to identify risky API calls which may potentially lead to runtime exceptions. Runtime exceptions may occur either because

1. an API lacks sufficient documentation,or
2. usage of the API does not conform to the specification, or
3. API wrapper does not indicate the API specification as part of its own specification.

The prototype then automatically generates test cases which show how such exceptions may be triggered.

Observation:

For commons-lang, JDK APIs were analyzed. It seems that the failing methods do not handle the potential runtime exceptions which may or may not have been declared/documented for the JDK APIs they invoke.

Possible fixes:

1. The failing methods under test could add internal checks on the values they forward to the JDK APIs.
2. The failing methods could handle the exceptions by adding relevant try/catch blocks.
3. The failing methods under test could specify the potential exceptions by adding @throws in their documentation/method signatures.

Issue Links

• relates to: LANG-1631 Add short circuits in CharSequenceUtils if a character is not defined