[News.eclipse.test-and-performance] Re: Only dynamic tests?

["Gian Franco Bonini" <gian.franco.bonini@xxxxxxx>]

Jan,
you can use e.test-and-performance, e.t.hyades, or the mailing list
(hyades-dev). In terms of traffic and participation, the last two options
are the best.

Gian Franco

"Jan Karstens" <jan.karstens@xxxxxx> wrote in message
news:cdj80h$aai$1@xxxxxxxxxxxxxx
> Hi Gian,
>
> thank you for your hint. Is this or the e.t.hyades forum the right place
> to post suggestions for static testing features?
>
> Jan
>
> Gian Franco Bonini wrote:
>
> > Hi Jan,
> > Static tests are in scope for Hyades 3.x (for a tentative post-3.0
feature
> > list, see
> > http://www.eclipse.org/hyades/ --> Documents --> Hyades features list
for
> > beyond 3.0).
> > According to the plan, Hyades will produce a specification document
> > (requirements, use cases) as part of release 3.1. Implementation
activity is
> > currently scheduled for 3.3 (with intermediate priority)  and following
> > releases, based on interest and resources available. As of now, work
hasn't
> > really started, but we plan to do so soon, and we'd be happy to receive
any
> > input.
> >
> > Thanks,
> >
> > Gian Franco
> >
> >
> >
> > "Jan Karstens" <jan.karstens@xxxxxx> wrote in message
> > news:cdiorv$cpe$1@xxxxxxxxxxxxxx
> >
> >>Hi,
> >>
> >>I was browsing through the features of Hyades (if I understood it
> >>correct, Hyades is the basis for this project) and only found an
> >>infrastructure for dynamic testing.
> >>Are there any thoughts towards an infrastructure for static testing? If
> >>you already have the project with the cod in eclipse, it would be great
> >>to have some sort of Code Quality Management Monitor. I'm thinking of a
> >>GUI that is extensible by plugins that collect meaningful information
> >>based on code analysis (there are already heaps of plugins out there,
> >>but not unified). Such a monitor would allow the user to get a quick
> >>grasp of possible problem areas and historic development of core
> >
> > indicators.
> >
> >>If there are thought to work in that direction, I would be happy to
> >>contribute ideas and requirements.
> >>
> >>Jan Karstens
> >
> >
> >