Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-6263

Test Scenario - expected vs actual alert is misleading

XMLWordPrintable

    • 2021 Week 13-15 (from Mar 29)
    • 1
    • Hide
      1. Open sample Traffic violation project.
      2. Open Violation Scenarios
      3. Change first expected fine form 500 to 501
      4. Run scenario and click View Alerts

      There will be an alert:

      • #1: Above speed limit: 10km/h and 30 km/h(AbstractScenarioRunner) : #1 Above speed limit: 10km/h and 30 km/h: Failed in "Fine.Amount": The expected value is "500" but the actual one is "501"

      However there should be an alert:

      • #1: Above speed limit: 10km/h and 30 km/h(AbstractScenarioRunner) : #1 Above speed limit: 10km/h and 30 km/h: Failed in "Fine.Amount": The expected value is "501" but the actual one is "500"
      Show
      Open sample Traffic violation project. Open Violation Scenarios Change first expected fine form 500 to 501 Run scenario and click View Alerts There will be an alert: #1: Above speed limit: 10km/h and 30 km/h(AbstractScenarioRunner) : #1 Above speed limit: 10km/h and 30 km/h: Failed in "Fine.Amount": The expected value is "500" but the actual one is "501" However there should be an alert: #1: Above speed limit: 10km/h and 30 km/h(AbstractScenarioRunner) : #1 Above speed limit: 10km/h and 30 km/h: Failed in "Fine.Amount": The expected value is "501" but the actual one is "500"
    • Undefined
    • NEW
    • NEW

      This issue is about alerts we provide once Test Scenario fails. Such alert contains usually message about what value was expected and what was the actual value. The issue is these values are ex-changed.

              yamer@redhat.com Yeser Amer
              rh-ee-jomarko Jozef Marko (Inactive)
              Jan Stastny Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: