• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • won't fix
    • CEP Plugin
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Current status:

      Due to a nature of GWT framework which translates Java code into JavaScript so that it can be ran in a browser, it's not possible to use Clover for client side code, especially for integration testing (by integration testing I mean tests running in browsers).

      It's possible to use Clover to instrument server-side code.

      It's also possible to use Clover to instrument client-side code, but only under a condition that tests will be running in a container simulating the browser:

      Related articles:
      https://confluence.atlassian.com/display/CLOVER/Using+Clover-for-Ant+with+GWT
      https://confluence.atlassian.com/display/CLOVER/Using+Clover+with+the+GWT-maven+plugin

      Scope:

      • publish source code of coverage recorder classes so that GWT framework could instrument them
      • we may need a new kind of a coverage recorder which would be able to run inside a browser - where to put coverage data files? etc ...
      • we may need some integrations with GWT compiler / tools

            [CLOV-585] Support GWT

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3342500 ] New: JAC Suggestion Workflow 3 [ 3584992 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Epic Name Original: gwt
            Epic Status Original: To Do [ 11732 ]
            Workflow Original: New Clover Workflow - Restricted [ 1474117 ] New: JAC Suggestion Workflow [ 3342500 ]
            Issue Type Original: Epic [ 19 ] New: Suggestion [ 10000 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Owen made changes -
            Workflow Original: New Clover Workflow [ 897606 ] New: New Clover Workflow - Restricted [ 1474117 ]
            Marek Parfianowicz made changes -
            Fix Version/s New: won't fix [ 38394 ]
            Fix Version/s Original: someday [ 23593 ]
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895274 ] New: New Clover Workflow [ 897606 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 176927 ] New: Clover Workflow [ 895274 ]
            Marek Parfianowicz made changes -
            Description Original: *Current status:*

            Due to a nature of GWT framework which translates Java code into JavaScript so that it can be ran in a browser, it's not possible to use Clover for client side code, especially for integration testing (by integration testing I mean tests running in browsers).

            It's possible to use Clover to instrument server-side code.

            It's also possible to use Clover to instrument client-side code, but only under a condition that tests will be running in a container simulating the browser:

            Related articles:
                https://confluence.atlassian.com/display/CLOVER/Using+Clover-for-Ant+with+GWT
                https://confluence.atlassian.com/display/CLOVER/Using+Clover+with+the+GWT-maven+plugin

            *Scope:*
             * publish source code of coverage recorder classes so that GWT framework could instrument them
             * we may need a new kind of a coverage recorder which would be able to run inside a browser - where to put coverage data files? etc ...
            New: *Current status:*

            Due to a nature of GWT framework which translates Java code into JavaScript so that it can be ran in a browser, it's not possible to use Clover for client side code, especially for integration testing (by integration testing I mean tests running in browsers).

            It's possible to use Clover to instrument server-side code.

            It's also possible to use Clover to instrument client-side code, but only under a condition that tests will be running in a container simulating the browser:

            Related articles:
                https://confluence.atlassian.com/display/CLOVER/Using+Clover-for-Ant+with+GWT
                https://confluence.atlassian.com/display/CLOVER/Using+Clover+with+the+GWT-maven+plugin

            *Scope:*
             * publish source code of coverage recorder classes so that GWT framework could instrument them
             * we may need a new kind of a coverage recorder which would be able to run inside a browser - where to put coverage data files? etc ...
             * we may need some integrations with GWT compiler / tools
            Marek Parfianowicz made changes -
            Backlog Order (Obsolete) Original: 1550000000
            Epic Name New: gwt
            Epic Status New: To Do [ 11732 ]
            Parent Original: CLOV-575 [ 86706 ]
            Issue Type Original: Sub-task [ 6 ] New: Epic [ 19 ]
            Marek Parfianowicz made changes -
            Description New: *Current status:*

            Due to a nature of GWT framework which translates Java code into JavaScript so that it can be ran in a browser, it's not possible to use Clover for client side code, especially for integration testing (by integration testing I mean tests running in browsers).

            It's possible to use Clover to instrument server-side code.

            It's also possible to use Clover to instrument client-side code, but only under a condition that tests will be running in a container simulating the browser:

            Related articles:
                https://confluence.atlassian.com/display/CLOVER/Using+Clover-for-Ant+with+GWT
                https://confluence.atlassian.com/display/CLOVER/Using+Clover+with+the+GWT-maven+plugin

            *Scope:*
             * publish source code of coverage recorder classes so that GWT framework could instrument them
             * we may need a new kind of a coverage recorder which would be able to run inside a browser - where to put coverage data files? etc ...
            Marek Parfianowicz made changes -
            Link New: This issue is related to CLOV-1454 [ CLOV-1454 ]

              mparfianowicz Marek Parfianowicz
              mstudman Michael Studman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 40h
                  40h
                  Remaining:
                  Remaining Estimate - 40h
                  40h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified