[
https://issues.apache.org/jira/browse/SANDBOX-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedikt Ritter updated SANDBOX-362:
------------------------------------
Attachment: SANDBOX-362-ConstructorTestCase.txt
Hi again,
I have attached a patch for ConstructorTestCase. Summary:
* moved expected failure cases to own test methods
* added test methods for null arguments
* added ExceptedException test rule to verify that correct exceptions are thrown
I still don't like, that some methods test more than one constructor. Maybe we
should create separate methods for those.
I also changed an exception message in DefaultClassAccessor from
"No such accessible constructor on object:"
to
"No such accessible constructor on class:"
because I think that this is more convenient.
Regards
Benedikt
> Create basic unit tests for all classes
> ---------------------------------------
>
> Key: SANDBOX-362
> URL: https://issues.apache.org/jira/browse/SANDBOX-362
> Project: Commons Sandbox
> Issue Type: Test
> Components: BeanUtils2
> Affects Versions: Nightly Builds
> Reporter: Benedikt Ritter
> Attachments: ArgumentTest.zip, SANDBOX-362-BeanUtilsTest.txt,
> SANDBOX-362-ConstructorTestCase.txt,
> SANDBOX-362-RefactoringOfArgumentTest.txt,
> SANDBOX-362-RefactoringOfAssertionsTest.txt, SANDBOX-362-TypeUtilsTest.txt
>
>
> Back up all existing implementations with unit tests:
> * Argument
> * Assertions
> * BeanUtils
> * DefaultBeanAccessor
> * DefaultClassAccessor
> * MethodRegistry
> * TypeUtils
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
