On Wed, Oct 25, 2017 at 12:31 PM, Jesse Glick <[email protected]> wrote: > I actually prefer to do most integration testing using `JenkinsRule`
I suppose I should clarify that this refers to testing a specific feature or fix with awareness of its point of implementation. There is also a use case for ATH in terms of smoke-testing an overall user workflow from end to end looking for otherwise unforeseeable regressions or poor interactions among numerous components, but that is probably not what you were thinking of when you asked about testing a particular plugin. -- 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/CANfRfr1-q2nGAVWsogR%3DKVvyWKg4vV540W7La1s2NwUAwEcXcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
