Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-1999

Using Bavet in ConstraintVerifier fails tests without proper error message

XMLWordPrintable

    • Hide

      The error occurs for constraints that even just consist of a filter and a penalty.

      Attached is a class containing a Unit Test that demonstrates the issue.

      • download the attached class and load it into any environment that has OptaPlanner-core OptaPlanner-test and JUnit in the classpath
      • run the test with ConstraintStreamImplType set to DROOLS and see the test succeed
      • run the test with ConstraintStreamImplType set to BAVET and see the test fail
      Show
      The error occurs for constraints that even just consist of a filter and a penalty. Attached is a class containing a Unit Test that demonstrates the issue. download the attached class and load it into any environment that has OptaPlanner-core OptaPlanner-test and JUnit in the classpath run the test with ConstraintStreamImplType set to DROOLS and see the test succeed run the test with ConstraintStreamImplType set to BAVET and see the test fail
    • NEW
    • NEW

      Simple constraints created using the constraint streams succeed when using Drools as ConstraintStreamImplType but fail when Bavet is selected (unexpected penalty of zero).

      The documentation does indicate that Bavet is not feature complete yet, however a problem caused by a lack of implementation should fail with an appropriate error message instead of altering the test results "silently".

        1. BugTest.java
          4 kB

              Unassigned Unassigned
              somejonathan Jonathan Guenther (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: