Thread: [Mockobjects-java-users] Examples

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi are there any examples on how to use Mock Objects. I had a look at =
the documents but don't find it very useful.

I Chung,

Thank you for your interest in Mock Objects !
This is still a work in progress ... We are currently working hard on =
the documentation as we agree with your comment that it is the weak =
point ...

However, the best documentation are examples and these are available as =
part of the distribution. The latest available released distribution is =
0.0.09. Have a look and post any question you have here. We'll be happy =
to answer them.

We are also interested by your feedback. You said you don't find the doc =
useful. What kind of doc would you like to see first so that we can =
concentrate our efforts on that.

Thanks
-Vincent
  ----- Original Message -----=20
  From: ch...@fr...=20
  To: moc...@li...=20
  Sent: Wednesday, August 15, 2001 10:00 AM
  Subject: [Mockobjects-java-users] Examples

  Hi are there any examples on how to use Mock Objects. I had a look at =
the documents but don't find it very useful.

All I want is a really simple working example that I can compile and =
run. This will help me to visualise how the classes within the =
mockobject packages are used.

Thanks
  ----- Original Message -----=20
  From: Vincent Massol=20
  To: moc...@li...=20
  Sent: Wednesday, August 15, 2001 10:34 AM
  Subject: Re: [Mockobjects-java-users] Examples

  I Chung,

  Thank you for your interest in Mock Objects !
  This is still a work in progress ... We are currently working hard on =
the documentation as we agree with your comment that it is the weak =
point ...

  However, the best documentation are examples and these are available =
as part of the distribution. The latest available released distribution =
is 0.0.09. Have a look and post any question you have here. We'll be =
happy to answer them.

  We are also interested by your feedback. You said you don't find the =
doc useful. What kind of doc would you like to see first so that we can =
concentrate our efforts on that.

  Thanks
  -Vincent
    ----- Original Message -----=20
    From: ch...@fr...=20
    To: moc...@li...=20
    Sent: Wednesda
y, August 15, 2001 10:00 AM
    Subject: [Mockobjects-java-users] Examples

    Hi are there any examples on how to use Mock Objects. I had a look =
at the documents but don't find it very useful.

ok, then download the distribution, there are plenty of examples.
Thanks
-Vincent
  ----- Original Message -----=20
  From: ch...@fr...=20
  To: moc...@li...=20
  Sent: Wednesday, August 15, 2001 10:42 AM
  Subject: Re: [Mockobjects-java-users] Examples

  All I want is a really simple working example that I can compile and =
run. This will help me to visualise how the classes within the =
mockobject packages are used.

  Thanks
    ----- Original Message -----=20
    From: Vincent Massol=20
    To: moc...@li...=20
    Sent: Wednesday, August 15, 2001 10:34 AM
    Subject: Re: [Mockobjects-java-users] Examples

    I Chung,

    Thank you for your interest in Mock Objects !=20
    This is still a work in progress ... We are currently working hard =
on the documentation as we agree with your comment that it is the weak =
point ...

    However, the best documentation are examples and these are available =
as part of the distribution. The latest available released distribution =
is 0.0.09. Have a look and post any question you have here. We'll be =
happy to answer them.

    We are also interested by your feedback. You said you don't find the =
doc useful. What kind of doc would you like to see first so that we can =
concentrate our efforts on that.

    Thanks
    -Vincent
      ----- Original Message -----=20
      From: ch...@fr...=20
      To: moc...@li...=20
      Sent: Wednesday, August 15, 2001 10:00 AM
      Subject: [Mockobjects-java-users] Examples

      Hi are there any example s on how to use Mock Objects. I had a =
look at the documents but don't find it very useful.

I'll have a look.
Cheers
  ----- Original Message -----=20
  From: Vincent Massol=20
  To: moc...@li...=20
  Sent: Wednesday, August 15, 2001 10:54 AM
  Subject: Re: [Mockobjects-java-users] Examples

  ok, then download the distribution, there are plenty of examples.
  Thanks
  -Vincent
    ----- Original Message -----=20
    From: ch...@fr...=20
    To: moc...@li...=20
    Sent: Wednesday, August 15, 2001 10:42 AM
    Subject: Re: [Mockobjects-java-users] Examples

    All I want is a really simple working example that I can compile and =
run. This will help me to visualise how the classes within the =
mockobject packages are used.

    Thanks
      ----- Original Message -----=20
      From: Vincent Massol=20
      To: moc...@li...=20
      Sent: Wednesday, August 15, 2001 10:34 AM
      Subject: Re: [Mockobjects-java-users] Examples

      I Chung,

      Thank you for your interest in Mock Objects !=20
      This is still a work in progress ... We are 
currently working hard =
on the documentation as we agree with your comment that it is the weak =
point ...

      However, the best documentation are examples and these are =
available as part of the distribution. The latest available released =
distribution is 0.0.09. Have a look and post any question you have here. =
We'll be happy to answer them.

      We are also interested by your feedback. You said you don't find =
the doc useful. What kind of doc would you like to see first so that we =
can concentrate our efforts on that.

      Thanks
      -Vincent
        ----- Original Message -----=20
        From: ch...@fr...=20
        To: moc...@li...=20
        Sent: Wednesday, August 15, 2001 10:00 AM
        Subject: [Mockobjects-java-users] Examples

        Hi are there any example s on how to use Mock Objects. I had a =
look at the documents but don't find it very useful.

I went to the MockObjects web site .... and noticed that version 0.01 was
released ! <argh>

We'll consider this first release as a try .... and forget about it. Now I
would like use to agree on the release process. Can you review all the
following point and tell me whether you agree or not so that we can reach a
consensus. Once this is done we'll put a page on the web site explaining the
release process. Thanks

P1 - Releasing a version is a community action that we all need to decide
together (the committers of the project). Before *any* release, we will need
to agree on doing a release. This entails sending a message on the mailing
list asking for a vote on the release (I propose to use the Apache Jakarta
system for voting : http://jakarta.apache.org/site/decisions.html).

P2 - Long before any release, we need to define what will go into that
release, i.e. the list of tasks that need to be performed *prior* to that
release. These tasks will be listed in the
http://mockobjects.sourceforge.net/todo.html (todo.xml file in CVS). Tasks
can be proposed on the mailing list (such as the mail I sent on 1st of
august, entitled "[Proposal] Roadmap". Unfortunately noone answered so these
tasks were not entered in the todo page. I'm still waiting for an ageement
before entering them !).

P3 - The changes page (http://mockobjects.sourceforge.net/changes.html,
changes.xml file in CVS) need to be up to date at any time. The goal of this
page is not to described fine-grained changes in CVS like "I have corrected
a typo" but rather to advertise changes that are useful to end users (for
example: "Improved the Mailing-list example by ..."). As it is very hard to
remember everything that everyone has done, it is mandatory to fill this
page as we do the modifications and not to wait till the release to fill it.
At the current time, this page is *NOT* up to date.

P4 - Check list of administrative tasks to perform before any release :

A1 - Agree on a release (see P1)
A2 - Designate a release manager for the current release to perform
A3 - Ensure that no one is working on any part of the files (code freeze).
This is done by posting a mail on the list asking for a code freeze.
A4 - Verify that the todo.html files is up to date
A5 - Verify that the changes.html file is up to date
A6 - Verify that the features page is up to date and includes all features
available in all releases + the new ones of this release. Note: This page
does not currently exist but we should create it quickly. This is the page
that persons will look at the most often to see what features the Mock
Objects project has.
A7 - Verify that the news items on the index page are up to date (major
announcement should be listed there, a release is a major announcement - A
news item should be added that says which version has been released with a
link pointing to the changes page)
A8 - Perform a Ant build 'dist' on the release manager's machine to ensure
everything build fine including the tests, web site generation, ...
A9 - Tag CVS (with the name MO_0_01_RELEASE - example for release 0.01)
A10- Publish the distributables files to SF. In the release note area of SF,
put a link to the changes page
A11- Increase the version number indicated in the build.xml file by 1 (for
example, after 0.01, put 0.02)
A12- Write a release announcement in the news area of SF (with a link to the
changes page)
A13- Send a message to mockobjects-java-user and -dev mailing lists to
announce the availability of the release
A14- (optional) Send announcements to other mailing-lists (XP mailing lists
on yahoogroups, JUnit mailing list) and web sites (junit.org, objectmentor,
...)

... then relax ! ;-)

I propose that we start doing this immediatly and follow this process for
the 0.02 release.
Thanks
-Vincent

Sorry this should have been posted to the -dev mailing list (I'm reposting)
Users please ignore ... :-)

----- Original Message -----
From: "Vincent Massol" <vm...@oc...>
To: <moc...@li...>
Sent: Wednesday, August 15, 2001 2:58 PM
Subject: [Mockobjects-java-users] [IMPORTANT] Release Process

> I went to the MockObjects web site .... and noticed that version 0.01 was
> released ! <argh>
>
> We'll consider this first release as a try .... and forget about it. Now I
> would like use to agree on the release process. Can you review all the
> following point and tell me whether you agree or not so that we can reach
a
> consensus. Once this is done we'll put a page on the web site explaining
the
> release process. Thanks
>
> P1 - Releasing a version is a community action that we all need to decide
> together (the committers of the project). Before *any* release, we will
need
> to agree on doing a release. This entails sending a message on the mailing
> list asking for a vote on the release (I propose to use the Apache Jakarta
> system for voting : http://jakarta.apache.org/site/decisions.html).
>
> P2 - Long before any release, we need to define what will go into that
> release, i.e. the list of tasks that need to be performed *prior* to that
> release. These tasks will be listed in the
> http://mockobjects.sourceforge.net/todo.html (todo.xml file in CVS). Tasks
> can be proposed on the mailing list (such as the mail I sent on 1st of
> august, entitled "[Proposal] Roadmap". Unfortunately noone answered so
these
> tasks were not entered in the todo page. I'm still waiting for an ageement
> before entering them !).
>
> P3 - The changes page (http://mockobjects.sourceforge.net/changes.html,
> changes.xml file in CVS) need to be up to date at any time. The goal of
this
> page is not to described fine-grained changes in CVS like "I have
corrected
> a typo" but rather to advertise changes that are useful to end users (for
> example: "Improved the Mailing-list example by ..."). As it is very hard
to
> remember everything that everyone has done, it is mandatory to fill this
> page as we do the modifications and not to wait till the release to fill
it.
> At the current time, this page is *NOT* up to date.
>
> P4 - Check list of administrative tasks to perform before any release :
>
> A1 - Agree on a release (see P1)
> A2 - Designate a release manager for the current release to perform
> A3 - Ensure that no one is working on any part of the files (code freeze).
> This is done by posting a mail on the list asking for a code freeze.
> A4 - Verify that the todo.html files is up to date
> A5 - Verify that the changes.html file is up to date
> A6 - Verify that the features page is up to date and includes all features
> available in all releases + the new ones of this release. Note: This page
> does not currently exist but we should create it quickly. This is the page
> that persons will look at the most often to see what features the Mock
> Objects project has.
> A7 - Verify that the news items on the index page are up to date (major
> announcement should be listed there, a release is a major announcement - A
> news item should be added that says which version has been released with a
> link pointing to the changes page)
> A8 - Perform a Ant build 'dist' on the release manager's machine to ensure
> everything build fine including the tests, web site generation, ...
> A9 - Tag CVS (with the name MO_0_01_RELEASE - example for release 0.01)
> A10- Publish the distributables files to SF. In the release note area of
SF,
> put a link to the changes page
> A11- Increase the version number indicated in the build.xml file by 1 (for
> example, after 0.01, put 0.02)
> A12- Write a release announcement in the news area of SF (with a link to
the
> changes page)
> A13- Send a message to mockobjects-java-user and -dev mailing lists to
> announce the availability of the release
> A14- (optional) Send announcements to other mailing-lists (XP mailing
lists
> on yahoogroups, JUnit mailing list) and web sites (junit.org,
objectmentor,
> ...)
>
> ... then relax ! ;-)
>
> I propose that we start doing this immediatly and follow this process for
> the 0.02 release.
> Thanks
> -Vincent
>
>
>
> _______________________________________________
> Mockobjects-java-users mailing list
> Moc...@li...
> http://lists.sourceforge.net/lists/listinfo/mockobjects-java-users
>

Here is a list of tasks that I propose for Release 0.02. Can you please
state your agreement and others that would like to see. I'll wait for your
approval before entering them in the todo page :

T1 - [doc] What are MockObjects?
T2 - [doc] Difference between MO and Stubs ?
T3 - [doc] Goal page that explains short term and long term goals of the
project
T4 - [doc] Coding conventions (in a "Developer" menu)
T5 - [doc] Features page
T6 - [doc] Release process page (in a "Developer" menu)
T7 - [code] add javadoc to all code where needed + add version number to
sources (@version @version@) + packages.html + overview.html
T8 - [code] Code aligned with coding conventions (and MO naming conventions
already present on the web site)
T9 - [build] finalized build process (still need to finalize directory
structure + manage examples + manage extensions)

These are the "mnimum" set of task that is can we before the release 0.02.

Tell me also if you wish to volunteer for a given task. There can be several
persons volunteering for the same task.

I volunteer for T2, T4, T6, T9.

Thanks
-Vincent

Sorry this should have been posted to the -dev mailing list (I'm reposting)
Users please ignore ... :-)

----- Original Message -----
From: "Vincent Massol" <vm...@oc...>
To: <moc...@li...>
Sent: Wednesday, August 15, 2001 3:07 PM
Subject: [Mockobjects-java-users] [Proposal] List of tasks for release 0.02

> Here is a list of tasks that I propose for Release 0.02. Can you please
> state your agreement and others that would like to see. I'll wait for your
> approval before entering them in the todo page :
>
> T1 - [doc] What are MockObjects?
> T2 - [doc] Difference between MO and Stubs ?
> T3 - [doc] Goal page that explains short term and long term goals of the
> project
> T4 - [doc] Coding conventions (in a "Developer" menu)
> T5 - [doc] Features page
> T6 - [doc] Release process page (in a "Developer" menu)
> T7 - [code] add javadoc to all code where needed + add version number to
> sources (@version @version@) + packages.html + overview.html
> T8 - [code] Code aligned with coding conventions (and MO naming
conventions
> already present on the web site)
> T9 - [build] finalized build process (still need to finalize directory
> structure + manage examples + manage extensions)
>
> These are the "mnimum" set of task that is can we before the release 0.02.
>
> Tell me also if you wish to volunteer for a given task. There can be
several
> persons volunteering for the same task.
>
> I volunteer for T2, T4, T6, T9.
>
> Thanks
> -Vincent
>
>
> _______________________________________________
> Mockobjects-java-users mailing list
> Moc...@li...
> http://lists.sourceforge.net/lists/listinfo/mockobjects-java-users
>