Stephen,
You suggest strictly separating UI tests and behavior tests, but using
backdoor manipulation/verification via xml configuration is no longer
end-to-end testing. Not to mention that plugin config is not exposed to
user as XML. Plus, if we move test fixtures to xml and the plugin
persistence evolves (as in this case), we are testing that plugin is able
to load obsolete config and not that it can be configured to do the same
using its new version.
Also note that with all the test we currently have, only a small part of
Jenkins UI is covered. The goal of covering UI in small portion of tests
and then focusing on the behavior does not sound achievable to me. In
effect we will have less UI coverage.
--
oliver
--
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].
For more options, visit https://groups.google.com/d/optout.
