Re: RW repository general questions - issues

Round 2. *1.* *DOM testing* *1.1* First thing, currently it can just tell me that something changed. But with my knowledge I can not say whether it is a bug or just some component upgrade (bootstrap, ...). Therefore I am wondering whether    you have some big plans with it ? I am also quite afraid of maintainability of such tests. Should I file an issue when such test fails, or should I just correct the test when I think that it is not a bug ? What kind of changes do you things in general are bugs ? *1.2* Secondly, when such test fails, it pollutes the log with whole dom of the expected and actual results. It makes other tests quite unreadable. Proposition: play with logging features (preffered), or make the DOM testing separate from the normal jasmine tests. *2.* *Jasmine Waitings* *2.1.* Should not we somehow abstract the timeout which is set to the waitings methods ? Have we already encountered some differences between local and CI test execution ? I am for some kind of ancestor of all tests, which would define e.g. timeout constants and other. *2.2* Have you considered using jasmine.async ? Using of it makes +waits+ methods redundant imho. Here (http://www.htmlgoodies.com/html5/javascript/using-the-done-method-in-your...) is nice blog about it. *3. Tests reusability* *3.1.* I have already mentioned common ancestor for tests. Do you think that it is feasible in JS in a nice way ? I think that for example testing of callbacks can be somehow abstracted and thus tests will be a little bit DRYer. *3.2* What about introducing Page Fragments into the tests ? For example selecting of an +pickList+ item requires following:             item.trigger('mousedown');             item.trigger('mouseup'); Similar things can be nicely encapsulated IMHO. I would like to ask you again for your insight, which of the above deserves issues submitting ? Posted by forums Original post: https://community.jboss.org/message/844145#844145