junit.framework.AssertionFailedError: Exactly one plugin expected in the step plugin input category expected:<1> but was:<38>

Pentaho BI Platform Tracking | Pavel Sakun | 3 years ago
  1. 0

    Bug 68940 – One addition expected:<1> but was:<0>

    netbeans.org | 1 year ago
    junit.framework.AssertionFailedError: One addition expected:<1> but was:<0>
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    Comment on revision r14281 in selenium

    Google Groups | 5 years ago | sele...@googlecode.com
    junit.framework.AssertionFailedError: expected:<org.openqa.selenium.remote.RemoteWebElement@38> but was:<org.openqa.selenium.remote.RemoteWebElement@39>
  4. 0

    Is Robotium reliable for testing how fast activities and fragments start?

    Stack Overflow | 3 years ago | Dan J
    junit.framework.AssertionFailedError: Step was too slow, expected 500ms but took 2079ms

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. junit.framework.AssertionFailedError

      Exactly one plugin expected in the step plugin input category expected:<1> but was:<38>

      at org.pentaho.di.core.plugins.PluginRegistryTest.testPluginRegistry()
    2. org.pentaho.di
      PluginRegistryTest.testPluginRegistry
      1. org.pentaho.di.core.plugins.PluginRegistryTest.testPluginRegistry(PluginRegistryTest.java:135)
      1 frame