Hello, I would like to post update on End-to-end WebDriver testing, since the tests have achived a milestone. They are running on Travis.
- Reported DISPATCH-745 <https://issues.apache.org/jira/browse/DISPATCH-745> about Hawtio console being completely broken following resolution of the issue, committed updated WebDriver tests to master - Test sources: https://github.com/jdanekrh/dispatch-console-tests - Travis CI build (executed on every commit to the tests): https://travis-ci.org/jdanekrh/dispatch-console-tests <https://travis-ci.org/jdanekrh/dispatch-console-tests> The build runs Chrome and Firefox with hawtio and stand-alone versions of console. Meaning 4 jobs in total. There is still those 10 tests as before, nothing new there. - Reported failure in TestConnectPage::test_wrong_ip,port as DISPATCH-746 <https://issues.apache.org/jira/browse/DISPATCH-746> - Reported minor issue regarding the treeview in hawtio in DISPATCH-748 <https://issues.apache.org/jira/browse/DISPATCH-748>, the single test for the treeview in hawtio (TestOverviewPage::test_expanding_tree) is still broken (it used to fail only in IE, now it fails in Firefox and Chrome, did not test IE) Regarding nightly tests, - Travis CI job which builds nightly docker images: https://github.com/msgqe/travisci/tree/qpid-dispatch-nightly-build <https://github.com/msgqe/travisci/tree/qpid-dispatch-nightly-build> - The images: https://hub.docker.com/r/jdanekrh/dispatch-console/tags/, https://hub.docker.com/r/jdanekrh/dispatch-router/tags/ <https://hub.docker.com/r/jdanekrh/dispatch-router/tags/> - Travis CI job which uses the images to run tests: https://github.com/msgqe/travisci/tree/qpid-dispatch-console-nightly-test <https://github.com/msgqe/travisci/tree/qpid-dispatch-console-nightly-test> This nightly build/test thing works thanks to the new Travis feature allowing to set periodical daily/weekly/monthly auto-triggering of a job. The idea is that the nightly build/test will alert about incompatibilities, changes and so on. This way, current version of dispatch is always tested. Furthermore, tests can be maintained the moment a problem appears, instead having to tackle multiple problems at once every time the tests are revisited. For example, upgrading Tomcat, or responding to some UI change in the dispatch plugin. Future intents - wait to see what is the priority on resolving reported issues. If they are not on the short term radar, eventually place an xfail annotation on the related tests, to make checking results easier; or just skip them using the @pytest.mark. mechanism. Not sure which yet. Probably latter. - think about which repo should hold dockerfiles, webdriver tests, and testing scripts. Currently, there is some duplication between nightly test repo and the main repo - write new test for the last subissue on DISPATCH-745 <https://issues.apache.org/jira/browse/DISPATCH-745>, adding charts to dashboard; it would cover a lot of new ground - continue posting updates publicly hoping to get collaboration going - use https://github.com/jdanekrh/dispatch-console-tests/issues for todos, so that I have autonomy for myself and visibility for everybody else - fix the three things reported there Answering why I did not use Sauce Labs. When I looked at it the last time, it could not connect websocket through that proxy of theirs. Dispatch needs that. I am not aware of any free service with websocket support. Cheers, -- Jiří Daněk Messaging QA
