We need Xvfb and Firefox in order to run the integration tests. And still, I don't think that this will increase our code coverage ratio. In order to correctly measure that, the test coverage tool needs to do dynamic analysis for finding out what gets tested and I doubt that it does that.
Uli On 03.03.2011 22:43, Kalle Korhonen wrote: > First report available: > http://analysis.apache.org/dashboard/index/48022 - mirrors the results > that Andreas linked to (selenium tests fail). > > Kalle > > > On Thu, Mar 3, 2011 at 1:26 PM, Kalle Korhonen > <[email protected]> wrote: >> No, not sure. I doubt the Selenium tests run regardless of Maven >> version. Yes, site and reports configuration would need to be changed >> for 3.x but that's separate. Figured I'll open the case first, see how >> far we get and meanwhile try it out locally. >> >> Kalle >> >> >> On Thu, Mar 3, 2011 at 1:15 PM, Ulrich Stärk <[email protected]> wrote: >>> You sure that Maven 3.0.2 will run the tests correctly? Last time I tried I >>> had problems generating >>> the site and running the component report with 3.0.2 but that might be a >>> completely different beast. >>> >>> Uli >>> >>> On 03.03.2011 21:57, Kalle Korhonen wrote: >>>> Yeah, claiming any absolute number is tricky. It depends on how and >>>> what you are looking at, but for the core alone, these coverage levels >>>> (see >>>> http://tapestry.apache.org/tapestry5.2-dev/tapestry-core/cobertura/index.html) >>>> are among the best I've ever seen in any project of similar size. >>>> Opened INFRA issue https://issues.apache.org/jira/browse/INFRA-3487 >>>> >>>> Kalle >>>> >>>> >>>> On Thu, Mar 3, 2011 at 12:46 PM, Andreas Andreou <[email protected]> wrote: >>>>> i remember seeing tapestry stats too somewhere... >>>>> yep, here they are (for 5.3.0-SNAPSHOT): >>>>> http://nemo.sonarsource.org/dashboard/index/14 >>>>> >>>>> It reports a code coverage of 45,0% but that's probably because >>>>> it can't run the browser based tests (also explains the 758 skipped tests) >>>>> >>>>> In the design menu, you'll see lot's of dependency cycles (in the package >>>>> level) >>>>> but overal the rules compliance (whatever that means) seems very good >>>>> >>>>> On Thu, Mar 3, 2011 at 22:23, Igor Drobiazko <[email protected]> >>>>> wrote: >>>>>> It's amazing. The most Apache projects have a coverage under 50%. >>>>>> >>>>>> On Thu, Mar 3, 2011 at 8:24 PM, Kalle Korhonen >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> I just noticed there's a Sonar instance running at >>>>>>> http://analysis.apache.org/. Could we get Tapestry on it? I'd ask for >>>>>>> permissions myself but I'm pretty sure access is restricted to PMC >>>>>>> members. >>>>>>> >>>>>>> Kalle >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best regards, >>>>>> >>>>>> Igor Drobiazko >>>>>> http://tapestry5.de >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Andreas Andreou - [email protected] - http://blog.andyhot.gr >>>>> Apache Tapestry PMC / http://chesstu.be owner >>>>> Open Source / JEE Consulting >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
