[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [starter-dev] March Minutes and Action
|
Testing the UI is indeed the most important part and it is not so
easy given all the input and flow possibilities. That's why I am
asking for help.
By testing the UI, you are indirectly testing the archetype
(especially if you are checking the generated project too).
However, you can also invoke the archetype directly, without the
web UI:
https://github.com/eclipse-ee4j/starter#generate-jakarta-ee-project-using-archetypes.
That should be tested too for unforeseen bugs. I think it's lower
priority as it appears to be in pretty stable state now.
Does this help?
On 3/13/2023 6:18 PM, Nikita Koselev
wrote:
I can commit, but I do not really know what
"testing the archetype" means in this context.
there are so many different combinations to test.
For example - we could test if archetype gets successfully
deployed to all types of EE servers mentions, with any
combination of the radio buttons possible (quite a lot of
combinations).
So I will really appreciate some guidance to help me focus.
--
Kind regards,
Nikita Koselev
_______________________________________________
starter-dev mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev