Re: [jdt-dev] Generalize JUnit view?

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

Hi Christian

The approach depends
on the goal. Do we want a simple generic view that can be easily used/enhanced
by a new test framework. or do want to allow each (new) test framework
to provide its own look and feel inside a single view. The former will
then most likely not be able to lift all feature of a given test framework,
like e.g. the JUnit view currently does for JUnit.

Debug seems a
reasonable home.

Dani



From:
       Christian
Pontesegger <christian.pontesegger@xxxxxx>
To:
       "Eclipse
JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date:
       28.01.2019
20:44
Subject:
       Re:
[jdt-dev] Generalize JUnit view?
Sent
by:        jdt-dev-bounces@xxxxxxxxxxx

---

I was wondering what the best approach
would be. Should we go for one
Unit Test view which would be reused from all components? Or better
have a UnitTestComposite and some reusable command handlers which then
can be used for dedicated JUnit, C++Unit, ... views?

What would be the host project for these generalized components? Having
 a dependency to JDT might not be first choice for other languages.
Probably platform.debug or platform.ui might be good choices.

Once we have an idea how to proceed I can offer to start with the
prototype. Basically copy the current state and carve it out from JDT.
Once it is stable other projects could then move to the new API.

Christian
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev