You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Stephen Colebourne (JIRA)" <ji...@apache.org> on 2006/10/11 18:44:36 UTC

[jira] Commented: (IO-94) New Mock InputStream & Writer implementations

    [ http://issues.apache.org/jira/browse/IO-94?page=comments#action_12441493 ] 
            
Stephen Colebourne commented on IO-94:
--------------------------------------

This feels almost out of scope for [io], which I've always felt was for runtime io work.

Is there a use case that isn't as a mock object? Is so, then we can rename it, but adding a 'mock' class to a non-mock jar feels wrong.

If it stays, it needs to go in the release notes.

> New Mock InputStream & Writer implementations
> ---------------------------------------------
>
>                 Key: IO-94
>                 URL: http://issues.apache.org/jira/browse/IO-94
>             Project: Commons IO
>          Issue Type: New Feature
>          Components: Streams/Writers
>            Reporter: Niall Pemberton
>         Assigned To: Niall Pemberton
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: MockInputStream.java, MockInputStreamTestCase.java
>
>
> I have created a MockInputStream which can be plugged in for testing parts of systems where the data doesn't matter - the main use I've had for it was testing large files - without actually having the InputStream process large amounts of bytes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org