Allow per-test coverage to be recorded across multiple JVMs

XMLWordPrintable

      Currently, Clover can only record per-test coverage if the tests are run in the same JVM as the application under test.

      Investigate the possibilities to enable Clover to communicate between JVMs. Prior to each testMethod, a flush message needs to be sent to the server under test with specific information test information.

        1.
        		 Integrate with JIRA's functional tests Sub-task Closed Marek Parfianowicz

        71%
        Original Estimate - 10h Original Estimate - 10h
        Time Spent - 10h Remaining Estimate - 4h
        2.
        		 Integrate with Confluence's functional tests Sub-task Closed Nick

        0%
        Original Estimate - 12h
        Remaining Estimate - 12h
        3.
        		 Create sample project with Maven2 and Ant builds for testing Sub-task Closed Nick  
        4.
        		 Merge from trunk to distributed branch, and then back to trunk Sub-task Closed Nick

        0%
        Original Estimate - 8h
        Remaining Estimate - 8h
        5.
        		 Audit logging in distributed coverage Sub-task Closed Nick

        0%
        Original Estimate - 4h
        Remaining Estimate - 4h
        6.
        		 guard to ensure there is only one reconection thread Sub-task Closed Nick

        0%
        Original Estimate - 1h
        Remaining Estimate - 1h
        7.
        		 add unit tests Sub-task Closed Nick

        0%
        Original Estimate - 16h
        Remaining Estimate - 16h
        8.
        		 consider JGroups V Cajo and drop one Sub-task Closed Nick

        0%
        Original Estimate - 8h
        Remaining Estimate - 8h
        9.
        		 encode initString with serverLocation property Sub-task Closed Nick  
        10.
        		 test on windows Sub-task Closed Nick

        0%
        Original Estimate - 8h
        Remaining Estimate - 8h
        11.
        		 Document possible need for Security policy to access System Properties: http://confluence.atlassian.com/display/CLOVER/Working+with+Restricted+Security+Environments Sub-task Closed Edwin Dawson [Atlassian]

        0%
        Original Estimate - 0.5h
        Remaining Estimate - 0.5h
        12.
        		 audit and update spec on EAC Sub-task Closed Nick

        0%
        Original Estimate - 8h
        Remaining Estimate - 8h
        13.
        		 Ability to toggle distributed coverage on/off at runtime -Dclover.distributed.coverage=OFF|ON Sub-task Closed Nick  
        14.
        		 document distributed coverage configuration options Sub-task Closed Edwin Dawson [Atlassian]

        0%
        Original Estimate - 2h
        Remaining Estimate - 2h
        15.
        		 don't pass Throwable on test failure Sub-task Closed Nick

        0%
        Original Estimate - 4h
        Remaining Estimate - 4h
        16.
        		 allow individual config options to be specified via System properties Sub-task Closed Nick

        0%
        Original Estimate - 2h
        Remaining Estimate - 2h

            Assignee:
            Nick
            Reporter:
            Nick
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 83.5h Original Estimate - 83.5h
                83.5h
                Remaining:
                Time Spent - 10h Remaining Estimate - 77.5h
                77.5h
                Logged:
                Time Spent - 10h Remaining Estimate - 77.5h
                10h