PASS -> ERROR
http://dstress.kuehne.cn/run/bug_20041225_A.d
http://dstress.kuehne.cn/run/bug_20041225_B.d
http://dstress.kuehne.cn/run/bug_20041225_C.d
http://dstress.kuehne.cn/run/bug_20041225_E.d
http://dstress.kuehne.cn/run/typeid_70.d
http://dstress.kuehne.cn/run/typeid_73.d
http://dstress.kuehne.cn/run/typeid_78.d

FAIL -> ERROR
http://dstress.kuehne.cn/run/opCmp_01.d

PASS: 686 -> 687
XPASS: 102 -> 104
FAIL: 162 -> 176
XFAIL: 323 -> 334
ERROR: 52 -> 24

Summary
http://dstress.kuehne.cn/www/dstress.html

Detailed
http://dstress.kuehne.cn/www/results.html

Thomas

Just curious ... what is your (Thomas K) "role" in 'D'? I've seen your posts related to dstress for some time, and have been impressed that there seems to be an organized way of noting bug reports and putting in some test(s) to ensure they don't pop up again once fixed.

I got 404's when I tried to look at several of the links ... http://dstress.kuehne.cn/run/bug_20041225_A.d http://dstress.kuehne.cn/run/bug_20041225_B.d http://dstress.kuehne.cn/run/bug_20041225_C.d

Is this activity something that a person could help with? Do you have a team already? Are you in some sense a digital-mars employee?

I'm a big believer in that part of XP (extreme programming) that is nearly obsessive about testing ... especially to faciltate 'refactoring'. Is this actually happening with D?

This newbie-non-cs-major tends to work out something using familiar concepts ... a "for" loop as an example. Get it working and then see how the "foreach" would be a better solution.

As another example, use a basic array approach, get it working, and then see how the AA would work possibly better. Having an xp-like test seems essential so you have enough confidence that they come up with the same, correct "answer".

Inquiring minds want to know <g>

And THANKS! for all your time and efforts on behalf of D.

In article <cuqbdo$uq6$1@digitaldaemon.com>, Lynn Allan says...
>
>Just curious ... what is your (Thomas K) "role" in 'D'? I've seen your posts related to dstress for some time, and have been impressed that there seems to be an organized way of noting bug reports and putting in some test(s) to ensure they don't pop up again once fixed.
>
>I got 404's when I tried to look at several of the links ... http://dstress.kuehne.cn/run/bug_20041225_A.d http://dstress.kuehne.cn/run/bug_20041225_B.d http://dstress.kuehne.cn/run/bug_20041225_C.d
>
>Is this activity something that a person could help with? Do you have a team already? Are you in some sense a digital-mars employee?
>
>I'm a big believer in that part of XP (extreme programming) that is nearly obsessive about testing ... especially to faciltate 'refactoring'. Is this actually happening with D?
>
>This newbie-non-cs-major tends to work out something using familiar concepts ... a "for" loop as an example. Get it working and then see how the "foreach" would be a better solution.
>
>As another example, use a basic array approach, get it working, and then see how the AA would work possibly better. Having an xp-like test seems essential so you have enough confidence that they come up with the same, correct "answer".
>
>Inquiring minds want to know <g>
>
>And THANKS! for all your time and efforts on behalf of D.
>
>

In article <cuqbdo$uq6$1@digitaldaemon.com>, Lynn Allan says...
>
>Just curious ... what is your (Thomas K) "role" in 'D'? I've seen your posts related to dstress for some time, and have been impressed that there seems to be an organized way of noting bug reports and putting in some test(s) to ensure they don't pop up again once fixed.
>
>I got 404's when I tried to look at several of the links ... http://dstress.kuehne.cn/run/bug_20041225_A.d http://dstress.kuehne.cn/run/bug_20041225_B.d http://dstress.kuehne.cn/run/bug_20041225_C.d

http://dstress.kuehne.cn/run/bug_20041226_A.d http://dstress.kuehne.cn/run/bug_20041226_B.d http://dstress.kuehne.cn/run/bug_20041226_C.d

>Is this activity something that a person could help with?
Finding bugs, writing and reviewing test cases... http://dstress.kuehne.cn/todo.txt

In case you are using MSWindows you might help by propperly porting
http://dstress.kuehne.cn/dstress.c
(throws up a popup notice for segfaulting test cases, thus it is useless for
scripted tests on MSWindows)

> Are you in some sense a digital-mars employee?
Not that I'm aware of - but I'm sure some financial support wouldn't hurt *g*

>I'm a big believer in that part of XP (extreme programming) that is nearly obsessive about testing ... especially to faciltate 'refactoring'. Is this actually happening with D?
>
>This newbie-non-cs-major tends to work out something using familiar concepts ... a "for" loop as an example. Get it working and then see how the "foreach" would be a better solution.
>
>As another example, use a basic array approach, get it working, and then see how the AA would work possibly better. Having an xp-like test seems essential so you have enough confidence that they come up with the same, correct "answer".
>
>Inquiring minds want to know <g>
It's not XP. At least nothing about refactoring D, maybe refactoring my own coding style ;)

I'm usually very sceptic about software without proper test cases. Almost every time I use "untested" software - be it open source or closed source - I run into major problems and either stop using or start fixing it.

Thomas

In article <cuvthm$isa$1@digitaldaemon.com>, Thomas Kuehne says... <snip>
>http://dstress.kuehne.cn/todo.txt
<snip>

Thomas, I noticed on the todo list to debug the cowell-shaw io test:

//	printf(" last line: %s", readLine);
printf(" last line: %.*s", readLine);

- Dave

Dave wrote:

| In article <cuvthm$isa$1@digitaldaemon.com>, Thomas Kuehne says...
| <snip>
|
|>http://dstress.kuehne.cn/todo.txt
|
| <snip>
|
| Thomas, I noticed on the todo list to debug the cowell-shaw io test:
|
| //	printf(" last line: %s", readLine);
| printf(" last line: %.*s", readLine);

Thanks :O

Thomas