Less painful per-test coverage updates

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Fixed
    • 3.0
    • Component/s: CIJ Plugin
    • None

      Faster incremental updates (ie don't reload all per-test data if only one additional test has been run).

      User-controlled updates (give user quick feedback on global coverage, invalidate per-test coverage in UI, allow them to reload that at their leisure).

          1.
          		 Don't reload all per-test data when some has been added Sub-task Closed Michael Studman (Inactive)  
          2.
          		 Updating test coverage UI can hog UI for very long time Sub-task Closed SlawekA (Inactive)

          0%
          Original Estimate - 8h
          Remaining Estimate - 8h
          3.
          		 regression - reload causes "passed tests only" coverage to be displayed improperly in coverage tree Sub-task Closed SlawekA (Inactive)  
          4.
          		 Restore SAMPLING PerTestCoverageStrategy in CIJ Sub-task Closed SlawekA (Inactive)  
          5.
          		 Introduce SparseBitSets to significantly reduce memory footprint Sub-task Closed SlawekA (Inactive)

          0%
          Original Estimate - 16h
          Remaining Estimate - 16h

              Assignee:
              Unassigned
              Reporter:
              Michael Studman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

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