On Wed, May 8, 2013 at 2:59 AM, Elmar Hinz wrote:
> To get started, I would need to do some more simple cases first.
Hi Elmar,
Did you make any progress on this? I know little about unit tests so I
won't be able to help much here, but I'm interested in any progress
you feel like sharing.
Scott
Hello Cyrille,
On Wed, May 8, 2013 at 1:28 AM, Cyrille Artho wrote:
> Hi Elmar,
> I think your plan covers the question "HOW do we want to unit test the
> software" well. However, we have not thought much about the "WHAT do we
> want to test?" question. Essentially, we need to think about which
Hi Elmar,
I think your plan covers the question "HOW do we want to unit test the
software" well. However, we have not thought much about the "WHAT do we
want to test?" question. Essentially, we need to think about which
classes/functions to test first.
I think it is not realistic to aim for a
> Ideally, one would not need to care about private variables because we
are only interested in that the public interface does what it is supposed
to do. Right ?
Yes, at least as far as it concerns the testing.
Denpendency Injection has other aspects.
As an example, if there is a class that prin
> I would like to see some examples of mocking and injection.
>
>
Thank you, Vincent,
> I tried to write some tests using the google framework, and started with
> the Buffer class. This immediately gives you the problem that it is
> dependent on a large number of other classes. So, this would me
On Tue, May 7, 2013 at 9:20 PM, Pavel Sanda wrote:
> Elmar Hinz wrote:
> > If somebody can give improvements to the plan, it's welcome.
>
> I guess people will let you do almost anything what you like in test/*
> but they will become much more picky when it comes to changes in src/.
> Perhaps the
Op 7-5-2013 10:57, Elmar Hinz schreef:
Hello list,
I'd like to come up with a small plan for getting started with unit
testing:
I would like to see some examples of mocking and injection.
I tried to write some tests using the google framework, and started with
the Buffer class. This immedi
Elmar Hinz wrote:
> If somebody can give improvements to the plan, it's welcome.
I guess people will let you do almost anything what you like in test/*
but they will become much more picky when it comes to changes in src/.
Perhaps the best way is to try example, post patch here and
and look what p
On Tue, May 7, 2013 at 5:58 PM, Richard Heck wrote:
> On 05/07/2013 04:57 AM, Elmar Hinz wrote:
>
>> Hello list,
>>
>> I'd like to come up with a small plan for getting started with unit
>> testing:
>>
>
> I am a total ignoramus when it comes to unit testing, so I will leave it
> to others
> who
On 05/07/2013 04:57 AM, Elmar Hinz wrote:
Hello list,
I'd like to come up with a small plan for getting started with unit
testing:
I am a total ignoramus when it comes to unit testing, so I will leave it
to others
who actually know something to express a view.
Richard
Hello list,
I'd like to come up with a small plan for getting started with unit testing:
==
1.) Directory structure: "tests/unit/"
==
* Unit tests stay their own directory separated from src/.
* Below "tests/unit" the directory structure mirrors th
11 matches
Mail list logo
