[
https://issues.apache.org/jira/browse/COLLECTIONS-811?focusedWorklogId=763421&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-763421
]
ASF GitHub Bot logged work on COLLECTIONS-811:
----------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/22 10:44
Start Date: 28/Apr/22 10:44
Worklog Time Spent: 10m
Work Description: kinow commented on PR #301:
URL:
https://github.com/apache/commons-collections/pull/301#issuecomment-1112055774
And didn't notice a difference in build time. Executed a few times locally
as well, and can confirm it doesn't bring any brittleness to our tests. Looks
like a good addition to our test code. Thanks for showing us this @ben-manes !
Issue Time Tracking
-------------------
Worklog Id: (was: 763421)
Time Spent: 40m (was: 0.5h)
> Consider integration Guava testlib tests
> ----------------------------------------
>
> Key: COLLECTIONS-811
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-811
> Project: Commons Collections
> Issue Type: Test
> Affects Versions: 4.4
> Reporter: Bruno P. Kinoshita
> Assignee: Bruno P. Kinoshita
> Priority: Minor
> Fix For: 4.5
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In COLLECTIONS-802 an issue reported was found with the help of Google Guava
> testlib tests.
> Maybe we could either have something similar (i.e. build ourselves?), use
> Google Guava's testlib, or find another similar solution. From what I
> understood, it uses a factory function to create an implementation of a
> collection interface (e.g. Map) and then runs a series of functional tests
> over the created object, failing tests if a contract is broken (e.g.
> iterating a map doesn't leave the next-object as null, as it was the case of
> the 802 issue).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
