Community
Participate
Working Groups
We had a problem this week where one of our pages completely failed to load (editor), but all JSUnit tests passed. This is because our current JS tests are only testing small units of functionality rather than entire pages. We should have some JS tests that at least ensure all our pages load, even if they don't test much of the page functionality.
This happened again this week, I released a bunch of command framework and client changes, and the sites page got broken. I had opened bug 364530 with the idea that we could run every command registered on a page as part of the test suite, but first we need this framework, where we run each page. It would be good to be able to specify something like... run page XXX and then run this function after it loads.
We started a smoke test page long ago, but never added much to it. http://wiki.eclipse.org/Orion/Manual_Test_Cases For 1.0 I think we need to beef up our smoke testing page to ensure that we are covering everything when we promote a build, test, etc. For comparison, look at the brackets smoke test page (which covers much less breadth of function but still more tests than our page) https://github.com/adobe/brackets/wiki/Brackets-Smoke-Tests
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
