This is the mail archive of the
ecos-bugs@sources.redhat.com
mailing list for the eCos project.
[Bug 19954] New: "Run Tests" output confusing
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at sources dot redhat dot com
- Date: Thu, 24 Apr 2003 17:08:27 +0100 (BST)
- Subject: [Bug 19954] New: "Run Tests" output confusing
http://bugs.ecos.sourceware.org/show_bug.cgi?id=19954
Summary: "Run Tests" output confusing
Product: eCos
Version: unknown
Platform: Other
OS/Version: Other
Status: UNCONFIRMED
Severity: normal
Priority: low
Component: ConfigTool
AssignedTo: jld at ecoscentric dot com
ReportedBy: nobody at cygnus dot com
There is no user documentation for the output of the
"Run Tests" option. Things like the numbers in the left margin,
and leading header before each test, need to be explained.
---------------------------------------------------------------------------
Originator:
Jonathan Larmour
Organization:
cygnus
Audit-Trail:
Responsible-Changed-From-To: alexs->sdf
Responsible-Changed-By: alexs
Responsible-Changed-When: Mon Apr 26 08:00:38 PDT 1999
Responsible-Changed-Why:
Simon, it is possibly best if you handle the documentation of this.
Thanks
-- Alex
State-Changed-From-To: open-feedback
State-Changed-By: sdf
State-Changed-When: Monday August 2 15:31:16 BST 1999
State-Changed-Why:
I am putting this into feedback because I think the issue is moot given the new Run Tests propertysheet dialog with
separate summary page.
Any remaining documentation issues should be dealt with in the user docs in the usual way.
From: Jonathan Larmour <jlarmour at cygnus dot co dot uk>
To: Simon FitzMaurice <sdf at cygnus dot co dot uk>
Cc: bugs at cygnus dot com
Subject: Re: ecc/19954
Date: Tue, 03 Aug 1999 11:50:46 +0000
Simon FitzMaurice wrote:
> -----Original Message-----
> From: jlarmour at cygnus dot co dot uk [mailto:jlarmour at cygnus dot co dot uk]
> > Simon FitzMaurice wrote:
> > >
> > > Synopsis: "Run Tests" output confusing
> > >
> > > State-Changed-From-To: open-feedback
> > > State-Changed-By: sdf
> > > State-Changed-When: Monday August 2 15:31:16 BST 1999
> > > State-Changed-Why:
> > > I am putting this into feedback because I think the issue is
> > moot given the new Run Tests propertysheet dialog with
> > > separate summary page.
> > > Any remaining documentation issues should be dealt with in the
> > user docs in the usual way.
> >
> > I presume this new Run Tests dialog is only in Churchill at this stage?
>
> No, the new dialog is in the standalone tool too - on the trunk, that is.
In that case I disagree that there is nothing more to do. Firstly the Help
button on that dialog does nothing. Secondly, when someone finds out that a
test *has* failed, they have to be able to parse the output to know why.
There is no description of the format of that output.
Perhaps you believe these are still user docs issues to be "dealt with in
the usual way", but that still doesn't make the problem go away.
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault
From: Jonathan Larmour <jlarmour at cygnus dot co dot uk>
To: Simon FitzMaurice <sdf at cygnus dot co dot uk>
Cc: bugs at cygnus dot com
Subject: Re: ecc/19954
Date: Tue, 03 Aug 1999 12:24:42 +0000
Simon FitzMaurice wrote:
>
> >
> > Firstly the Help button on that dialog does nothing.
> >
>
> This is a valid, but completely independent observation. Help buttons,
> where present, on all the dialogs should of course function but this PR
> complains about documentation of test output.
Would you like me to submit this as a separate CR, or will you deal with it
right away?
> > Secondly, when someone finds out that a test *has* failed, they have to be
> able to parse the output to know why.
>
> Indeed so, but this is not CT-specific. This is true however the tests are
> run, be that using the test tool as a standalone app, in the CT or on the
> command line. This is a general documentation requirement. By "the usual
> way" I mean as a documentation PR/CR.
We only document using eCosTestClient from within the Config Tool. There are
also a few other problems with the current docs too:
http://cygweb.cygnus.com/ecos/documentation/docset-latest/guides/user-guides/x807.html
Every function has "(void)" after it for some reason. There is no clear
description of what "NORESULT" means, etc.etc.
Anyway, in PRMS there are no separate "documentation" PRs - I believe what
you are wanting to do is assign this to roberte rather than close it. But I
believe you were assigned the PR as you are to provide the description to
Robert - *I* don't even know how to parse the first line of test output, so
I don't fancy Robert's chances. I have been assigned PRs which are clearly
doc only, but for the reason that I am to provide the documentation. Robert
just types it in.
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault
State-Changed-From-To: feedback-closed
State-Changed-By: jlemke
State-Changed-When: Mon Aug 13 13:47:36 PDT 2001
State-Changed-Why:
No response from customer. Fix presumed good.
State-Changed-From-To: closed-analyzed
State-Changed-By: jlarmour
State-Changed-When: Mon Aug 13 14:09:25 PDT 2001
State-Changed-Why:
Not closed for a sensible reason. There was no
fix - it was an internal PR so the state wasn't tracked exactly.
Responsible-Changed-From-To: sdf->jlarmour
Responsible-Changed-By: jlarmour
Responsible-Changed-When: Mon Aug 13 14:09:25 PDT 2001
Responsible-Changed-Why:
sdf has left
Unformatted:
Originator:
page: www.cygnus.com/product/ecc-pr.html
Send_PR_form: Sent_from_www.cygnus.com
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.