> Am 26.04.2022 um 18:28 schrieb Basil Crow <m...@basilcrow.com>:
> 
> On Tue, Apr 26, 2022 at 7:45 AM Ullrich Hafner <ullrich.haf...@gmail.com> 
> wrote:
> 
>> Those tests will run in a special docker container with a headless browser 
>> (chrome or firefox).
> 
> Ideally, I think we would want to support both Dockerized and
> non-Dockerized builds if possible. 

You can run the build locally without Docker. Docker is just used in CI (GitHub 
Action or Jenkins). I am locally using a different Maven profile and run the 
tests without Docker in Firefox or Chrome. You can even run it from IntelliJ 
and set breakpoints.

> 
>> […] run them as real system tests using a real browser and a real Jenkins 
>> instance and not as part of our integration tests with a fake UI (HTMLUnit) 
>> and a fake Jenkins (started via JTH) […]
> 
> Regarding the use of a "real Jenkins instance," I wonder how the ATH
> implementation compares to RealJenkinsRule, which is at a high level
> doing something very similar; namely, starting Jenkins in a separate
> Java process and tearing it down at the end of the test. If the
> RealJenkinsRule implementation is more efficient while still remaining
> compatible with the goal of frontend testing with a headless browser,
> it may be worth looking into unifying the two implementations in order
> to reduce maintenance and/or increase performance.
> 
>> not all plugins have UI tests yet, so there is an initial ramp up time 
>> required
> 
> I think if we build it they will come.
> 
>> […] UI tests are more fragile
> 
> Has this ever not been the case in the decades you and I have been
> programming? I guess the benefit of this idea depends on _how_
> fragile. If the fragility is occasional and a retry chases the problem
> away, that could be tolerable. On the other hand, if the fragility is
> frequent and requires one or more retries, this could undermine the
> idea.
> 
>> build execution times of PRs will increase since the initialization is slow
> 
> I wonder if some targeted optimization couldn't be done through the
> use of techniques such as the ones used in RealJenkinsRule.
> 
> Basil
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjphex3uXLfjsAfCpEaFvMNpXgBocgnX5tHaSuqTV1iZ7w%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/644842DF-A9B1-4D27-81F7-AE5598E3325B%40gmail.com.

Reply via email to