Kurt Sansom

I believe this is still an issue, I am creating a Dockerfile that builds pfunit from the release package. and fails on cmake. but it sounds like it is prefered...

thank you @tclune, that is exactly the information I think I needed. For now I am pushing toward the first suggestion, and as you mentioned I need to add information...

Thank you @tclune that was exactly what i needed to know about the `message` attribute.

Is there a good place to add an example like this in here or in the demos?

it appears to be happening on newer versions of git as well. e.g. git version 2.1.4

Thank you @tclune. That is very helpful information. I updated my first comment with more clear description of the test comparing two arrays with 1 element. Is there a debug...

I was looking at JUnit5, and read about `@BeforeEach` and `@BeforeAll`, I think pFUnit `@before` is analogous to `@BeforeEach`. Is there a decorator analogous to `@BeforeAll` in pFUnit?

I decided to rename the function to `approx` to simplify the name length, and mirror the name use by pytest as there doesn't appear to be an equivalent in JUnit....

I made a simple example on this branch. https://github.com/kurtsansom/pFUnit/tree/assert_alias map: ```py assert_alias_map = {'approx' : 'ApproxEqual'} ``` in `class AtAssert(Action):` ```py if (match.group(1).lower() in self.alias_map.keys()): function_name = self.alias_map[match.group(1).lower()] else: function_name...

I will shoot for getting to this by the end of the week.