gmane.comp.java.jmock.devel

Nat Pryce | 24 Aug 12:20

2.5.1 Released

We've just released jMock 2.5.1, a bug-fix release that improves error messages.

The changelog is at:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10336&styleName=Html&version=14527

--Nat

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

headers

Nat Pryce (JIRA | 24 Aug 02:02

[jira] Created: (JMOCK-200) JMock does not report actual invocations when the mockery is not satisfied

JMock does not report actual invocations when the mockery is not satisfied
--------------------------------------------------------------------------

                 Key: JMOCK-200
                 URL: http://jira.codehaus.org/browse/JMOCK-200
             Project: jMock
          Issue Type: Bug
          Components: Library
    Affects Versions: 2.5.0
            Reporter: Nat Pryce
            Priority: Minor

--

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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

headers

Nat Pryce (JIRA | 14 Aug 00:19

[jira] Created: (JMOCK-199) Upgrade to CGLIB 2.2

Upgrade to CGLIB 2.2
--------------------

                 Key: JMOCK-199
                 URL: http://jira.codehaus.org/browse/JMOCK-199
             Project: jMock
          Issue Type: Improvement
          Components: Library
    Affects Versions: 2.5.0
            Reporter: Nat Pryce
             Fix For: 2.6.0

--

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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

headers

Nat Pryce (JIRA | 13 Aug 18:22

[jira] Updated: (JMOCK-172) Make it easy to define a block of expectations that only occur in a given state


     [
http://jira.codehaus.org/browse/JMOCK-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce updated JMOCK-172:
----------------------------

    Priority: Minor  (was: Major)

> Make it easy to define a block of expectations that only occur in a given state
> -------------------------------------------------------------------------------
>
>                 Key: JMOCK-172
>                 URL: http://jira.codehaus.org/browse/JMOCK-172
>             Project: jMock
>          Issue Type: New Feature
>          Components: Library
>    Affects Versions: 2.4.0
>            Reporter: Nat Pryce
>            Priority: Minor
>
> If you want a bunch of expectations to only occur in a particular state, it's inconvenient to write "when"
clauses after each one.  It would be nice to specify the state(s) for an entire block of expectations, like this:
>     checking(new Expectations(foo.is("bar")) {{
>         ...
>     }}
> Perhaps a subclass of Expectations:
>     checking(new ExpectationsWhen(foo.is("bar")) {{
>         ...
>     }}

(Continue reading)

headers

Nat Pryce (JIRA | 9 Aug 10:48

[jira] Issue Comment Edited: (JMOCK-185) new will() methods for terse referring to parameters.


    [
http://jira.codehaus.org/browse/JMOCK-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128889#action_128889
] 

npryce edited comment on JMOCK-185 at 8/9/08 3:47 AM:
---------------------------------------------------------

This can also be achieved with the scripting extension which is in version 2.5.0. See issue JMOCK-174.

      was (Author: npryce):
    This can also be achieved with the scripting extension which is currently in SVN HEAD. See issue JMOCK-174.

> new will() methods for terse referring to parameters.
> -----------------------------------------------------
>
>                 Key: JMOCK-185
>                 URL: http://jira.codehaus.org/browse/JMOCK-185
>             Project: jMock
>          Issue Type: New Feature
>          Components: Library
>            Reporter: Paul Hammant
>            Priority: Trivial
>
> >Nat - I still think you should code something for this -
> >
> >   will(returnParamOfSameType());
> >   will(returnParam(0));
> >   will(returnParamOfType(Foo.class));
> It looks a good idea and easy to add.

(Continue reading)

headers

Nat Pryce (JIRA | 9 Aug 01:11

[jira] Resolved: (JMOCK-192) Support the new test runner architecture in JUnit 4.5


     [
http://jira.codehaus.org/browse/JMOCK-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce resolved JMOCK-192.
-----------------------------

    Resolution: Fixed

Committed to trunk

> Support the new test runner architecture in JUnit 4.5
> -----------------------------------------------------
>
>                 Key: JMOCK-192
>                 URL: http://jira.codehaus.org/browse/JMOCK-192
>             Project: jMock
>          Issue Type: Improvement
>          Components: Library
>    Affects Versions: 2.4.0
>            Reporter: Nat Pryce
>            Assignee: Nat Pryce
>             Fix For: 2.6.0
>
>
> JUnit 4.5 will have a new API for defining test runners.  JMock's test runner must be migrated to this new API.

--

-- 
This message is automatically generated by JIRA.
-

(Continue reading)

headers

Nat Pryce (JIRA | 9 Aug 00:55

[jira] Updated: (JMOCK-167) Don't report "returns a default value" for void methods


     [
http://jira.codehaus.org/browse/JMOCK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce updated JMOCK-167:
----------------------------

    Fix Version/s:     (was: 2.7.0)
                   2.6.0

> Don't report "returns a default value" for void methods
> -------------------------------------------------------
>
>                 Key: JMOCK-167
>                 URL: http://jira.codehaus.org/browse/JMOCK-167
>             Project: jMock
>          Issue Type: Improvement
>          Components: Library
>            Reporter: Steve Freeman
>            Assignee: Steve Freeman
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> When a void method isn't called, the error message looks like:
> expected exactly 1 time, never invoked: auction.join(); returns a default value
> The "returns a default value" is correct but confusing. We should either say "void" or nothing at all for
void methods

--

--

(Continue reading)

headers

Nat Pryce (JIRA | 8 Aug 20:47

[jira] Resolved: (JMOCK-195) mail archives are out of date


     [
http://jira.codehaus.org/browse/JMOCK-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce resolved JMOCK-195.
-----------------------------

    Resolution: Fixed

The developers list is being archived again.

> mail archives are out of date
> -----------------------------
>
>                 Key: JMOCK-195
>                 URL: http://jira.codehaus.org/browse/JMOCK-195
>             Project: jMock
>          Issue Type: Bug
>          Components: Website
>            Reporter: Sebastian Sickelmann
>            Assignee: Nat Pryce
>             Fix For: Chore (ASAP)
>
>
> the links to the mail archives are out of date.
> Link to 
> http://markmail.org/search/?q=list%3Aorg.codehaus.jmock.dev
> or 
> http://archive.jmock.codehaus.org/dev
> instead for the dev list.

(Continue reading)

headers

Nat Pryce (JIRA | 5 Aug 11:50

[jira] Resolved: (JMOCK-167) Don't report "returns a default value" for void methods


     [
http://jira.codehaus.org/browse/JMOCK-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nat Pryce resolved JMOCK-167.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.0

Fixed in subversion.

> Don't report "returns a default value" for void methods
> -------------------------------------------------------
>
>                 Key: JMOCK-167
>                 URL: http://jira.codehaus.org/browse/JMOCK-167
>             Project: jMock
>          Issue Type: Improvement
>          Components: Library
>            Reporter: Steve Freeman
>            Assignee: Steve Freeman
>            Priority: Minor
>             Fix For: 2.7.0
>
>
> When a void method isn't called, the error message looks like:
> expected exactly 1 time, never invoked: auction.join(); returns a default value
> The "returns a default value" is correct but confusing. We should either say "void" or nothing at all for
void methods

(Continue reading)

headers

MSanchez | 4 Aug 23:13

Build of revisions after 1193 fail


Hi

I'm trying to build from source but all (tried) revisions after r1193 fail

(output from r1280 build)
$ ant
Buildfile: build.xml

clean:
   [delete] Deleting directory /home/marcos/jmock/trunk/jmock2/build

dir.build:
    [mkdir] Created dir: /home/marcos/jmock/trunk/jmock2/build

compile:
    [mkdir] Created dir: /home/marcos/jmock/trunk/jmock2/build/classes
    [javac] Compiling 175 source files to
/home/marcos/jmock/trunk/jmock2/build/classes
    [javac]
/home/marcos/jmock/trunk/jmock2/src/org/jmock/lib/concurrent/DeterministicScheduler.java:28:
org.jmock.lib.concurrent.DeterministicScheduler is not abstract and does not
override abstract method <T>invokeAny(java.util.Collection<? extends
java.util.concurrent.Callable<T>>,long,java.util.concurrent.TimeUnit) in
java.util.concurrent.ExecutorService
    [javac] public class DeterministicScheduler implements
ScheduledExecutorService {
    [javac]        ^
    [javac] 1 error

(Continue reading)

headers

Marcos Sanchez (JIRA | 4 Aug 20:18

[jira] Created: (JMOCK-198) Allow assert of State-Machine

Allow assert of State-Machine
-----------------------------

                 Key: JMOCK-198
                 URL: http://jira.codehaus.org/browse/JMOCK-198
             Project: jMock
          Issue Type: Improvement
          Components: Library
    Affects Versions: 2.5.0
            Reporter: Marcos Sanchez
            Priority: Trivial

Asserting a state-machine's state requires the internal API (not obvious, clear or documented) as in
     assertTrue(stateMachine.is("desired-state").isActive());
     assertTrue(stateMachine.isNot("undesirable-state").isActive())

I suggest the creation of a become("state") counterpart. Maybe something like isCurrently("state") &
isNotCurrently("state") which wrap the internal API, such that we get
     assertTrue(stateMachine.isCurrently("state"));
     assertTrue(stateMachine.isNotCurrently("state"));

--

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

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

(Continue reading)

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31