I’m almost done with the refactoring of the acceptance tests for the Warnings Next Generation Plugin.
I created a PR (WIP), so you can already have a look at the tests: https://github.com/jenkinsci/acceptance-test-harness/pull/479 The tests work fine on Linux/Chrome and most times on macOS/Chrome and macOS/Firefox (sometimes I get timeouts). I still need to investigate why they not work on Linux/Firefox. One idea would be to move these tests to the Warnings Next Generation Plugin. Then I can use these tests to validate PRs to my plugin as well. > Am 07.01.2019 um 22:59 schrieb Ullrich Hafner <[email protected]>: > >> Am 07.01.2019 um 14:28 schrieb [email protected] >> <mailto:[email protected]>: >> >> Thank you all for your replies and insights! >> >> Ullrich, I totally agree with splitting tests but putting them into plugins >> would increase work for maintainers and contributors (as was mentioned by >> Mark). So in that case I wanted start with plugins which maintainer is aware >> of ATH and does not mind to do it. So your proposal is great, we can start >> with analysis plugins - choose the one plugin and see how it works if you >> agree. I will create jira for it. If it goes well, we can move tests into >> more plugins. > > Ok. With a slightly changed topic: since the analysis plugins are end-of-life > I would suggest to delete the tests all together. (Or keep some for LTS > testing since the plugins will still be used for some time). I created a set > of new tests for the warnings-ng plugin with students in the last summer > (https://github.com/uhafner/acceptance-test-harness/commits/hm-edu-testing > <https://github.com/uhafner/acceptance-test-harness/commits/hm-edu-testing>). > I still need to polish them a little bit before we can continue. (Currently > they are out-of-date since I changed some options in the 1.0 release.) I’m > not sure if I get that done in January... > >> >> Oliver, do you wish to move all tests of plugins from ATH or just those >> which are not very interesting from integration point of view (for example >> let there 1-3 tests for the most used scenarios of plugin which have a lot >> of installation)? I would let in ATH a few interested scenarios for most >> used plugins. On the other hand it is not such a problem to run the selenium >> tests for the most used plugins separately. What do you thing about it? >> >> Martin, it sounds great. You can count with me anytime you need any help >> with it. >> >> Regards, >> Lucie >> >> >> >> -- >> 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 [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/c8f2b5aa-4259-4d75-91f9-d910ad5341b2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/c8f2b5aa-4259-4d75-91f9-d910ad5341b2%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7D0AFA61-A15F-4F61-95F8-E09582A589EA%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
