All public methods should be tests regardless of name

Description

In MXUnit all public methods of a test CFC are run, but with TestBox's compat the specs must end (or maybe contain) the word "test." This is a compatibility issue because all test methods have to be renamed.

Activity

Show:
Ben Botto
June 5, 2018, 4:52 AM

Sorry to double report this. I searched through the issues, but not the closed ones. It looks like reports the same issue, but it was reported in 2013 and is closed. The issue was not resolved, though, and there's no documentation about this naming requirement.

Brad Wood
June 5, 2018, 5:01 AM

I think perhaps Luis was confused as to how MXUnit worked. The docs mention that the FILENAME must start or end with the word "test" but you are correct that

public methods are considered tests regardless of their name

https://github.com/mxunit/mxunit/wiki/Anatomy-of-a-TestCase

??

Brad Wood
June 5, 2018, 5:02 AM

Ben, I removed the text "MXunit compat" from the ticket and instead added the "MXunit Compatibility" component. Also, I reversed the confusing wording of the title to describe how it should work, not the incorrect current behavior.

Luis Majano
June 5, 2018, 7:37 AM

I think at this point I am not willing to invest in anymore MXUnit compatiblity due to the long time that has passed since we initially supported this. I would love a pull request, but I cannot justify adding resources or time for supporting MXUnit any longer.

Ben Botto
June 5, 2018, 7:41 AM

Yeah, that make sense. But, I'll add the same note I did to the last ticket. A brief note somewhere about the naming requirement would save a lot of time when migrating. I was fortunate in that the Slack community helped me resolve the issue pretty quickly, but I did spend about an hour trying to figure out why my tests weren't running prior to asking for help =)

Anyway, thanks for the response.

Won't Fix

Assignee

Luis Majano

Reporter

Ben Botto

Labels

None

Components

Priority

Major