Uploaded image for project: 'Code Tools'
  1. Code Tools
  2. CODETOOLS-7170394

Diagnostic of configuration inconsistency could be better

    Details

    • Type: Enhancement
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: jt4.5
    • Fix Version/s: TBD_Major
    • Component/s: tools
    • Labels:
    • Subcomponent:
    • CPU:
      generic
    • OS:
      generic

      Description

      JavaTest silently ignores some inconsistencies in configuration. Simple scenario:
      - configure a test suite with an Exclude list file specified
      - exit JavaTest
      - remove (move) .jtx file
      - start JT (previous configuration is restored without any warnings)
      - run tests (tests are executed in spite of .jtx is missing)

      The only way to see inconsistency is to open Exclude List interview. In this case JT won't allow to close the dialog unless the inconsistency is fixed.

      Perhaps, some mechanism to alarm user if something wrong with interview could be helpful. Exclude List is just partial case...

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                afedorch Alexey Fedorchenko (Inactive)
                Reporter:
                dfazunen Dmitry Fazunenko (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Imported:
                  Indexed: