Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests.