5 Replies Latest reply on Jul 9, 2008 3:50 PM by clebert.suconic

    Coverage on tests

    clebert.suconic

      I have compiled a list for missing tests or missing coverage:

      http://wiki.jboss.org/wiki/JBossMessagingCoverageTests

      I have used a WIKI, so we can all update it as we go, and I haven't linked it anywhere as the page should disappear when we complete writing the tests.

      For this I have used a mix of manual steps (Find reference of classes, and look for specific methods), looking at the list of methods and things done / comparing to the implementation.

      And also.. I've executed only the isolated test to find what is the covered by specific tests. Example:

      ant clean; ant -Dtest-mask=PostOfficeTest emma

      or if you want to run it faster

      rm build/emma/coverage.emma; ant -Dtest-mask=PostOfficeTest emma


      With that you can see exactly what methods are not being tested by PostOfficeTest. Just look for the class on the report.

      Emma was not in the center of what I did, but it was a good help.

      Also I will redo/refine the search next week after we have written more tests, making sure we are not missing anything.

        • 1. Re: Coverage on tests
          timfox

          Ok thanks for that.

          I have filled in some detail which you had missed out.

          • 2. Re: Coverage on tests
            timfox

            Good news is, we are almost there :)

            Let's split these up into who is handling what and add our names on the wiki so we don't step on each others toes...

            • 3. Re: Coverage on tests
              timfox

              Great progress to everyone who's been working on tests, we are almost there!

              Let's do final push today and tomorrow and get that wiki page completely cleared down by end of the week, then we have a clean slate for the F2F ready to start the rest of the work

              :)

              • 4. Super fast test suite
                timfox

                I want to say thanks to the team for a brilliant job in getting this done :)

                It isn't fun writing tests but now we can boast a test suite including 1500 pure unit tests that run in less than 10 seconds total !

                And a further 800 (?) integration, timing and concurrent tests that only take about 8 mins to run.

                This is going to make our lives a lot easier going ahead. No more three hour test runs.

                • 5. Re: Coverage on tests
                  clebert.suconic

                  What's even nicer is... no database setups.. no thirdparty manual downloads such as mysql driver or BerkleyDB.

                  Just checkout trunk, type ant.. and 15 seconds later you're done from compiling to running 1600 tests.