Tool suggestion: JTReg test module dependencies verifier.

Alexandre (Shura) Iline alexandre.iline at oracle.com
Wed Mar 28 18:34:35 UTC 2018



> On Mar 28, 2018, at 11:22 AM, Jonathan Gibbons <jonathan.gibbons at oracle.com> wrote:
> 
> 
> 
> On 3/28/18 10:57 AM, Alexandre (Shura) Iline wrote:
>>> There's a 3rd (weaker?) category of "implementation desires", such as whether or not or how much this is integrated into jtreg.
>> Correct, these are the non-functional requirements, of which at least one is missing right now:
>> 2. The tool must use jdeps tool or jdeps API to perform test selection and test execution.
> It's quibbling, but I don't think these are requirements. If jdeps or the jdeps API did not exist, you could still implement what you are proposing.  jdeps and the jdeps API are just technologies which you may elect to use to make your task simpler.

Well, it must be a requirement to treat modules in a way compatible with JDK. By requiring what I am requiring, I am guarantying that and also, in addition, since I am strongly opposed to re-implement what is already implemented in jdeps, this is my proposal for the tool: it must use jdeps.

Same, word for word, goes for JTReg, FWIW.

Shura
> 
> -- Jon



More information about the jtreg-dev mailing list