Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

notToBeBetween seems to be the same as toBeBetween

Description

Repro:

 

 

 

I suspect it's here:

 

You are being a bit "uncontrolled" in your catch there. You should only be catching whatever AssertionException that between might throw; you shouldn't be catching everything. Because you're also catching the exception fail throws here, and... that's yer problem! (thanks to for noticing the cause here. I missed it on first take!)

Activity

Show:

Luis Majano May 3, 2021 at 2:06 PM

Thanks guys!. Is a PR coming?

Brad Wood April 30, 2021 at 6:03 PM

Using Adam’s tests above (which need massaged into the testbox core test suite), the refactor of the expectation.toBeBetween() method seems to work

The trick is the final fail needs moved out of the try block or it gets swallowed as well

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Priority

Sentry

Created April 30, 2021 at 5:49 PM
Updated June 2, 2021 at 8:58 PM
Resolved June 2, 2021 at 8:58 PM