dlealv

WildHog on my fork I updated the `README.md` file with the changes I proposed. Thanks

Thanks, @WildH0g for taking the time to respond, I was working on some of the changes and I will update the source code, but before that, I have the following...

It looks you assumed I made the changes in the source code in GitHub, I did the changes I indicated in my comment on **my local copy waiting for some...

Hi, @WildH0g I updated the source code with the changes I mentioned and also the corresponding testing file. I included checking for preconditions against `undefined` for `assertEquals` just to show...

About extending `assert`, I read the article. I see how we can do it, the thing is the order or argument and the fact that `message` and `expectedResult` can both...

@WildH0g I have another question about the README file, you presented all the samples using this notation `()=>` why is that, I realized that the library works not using that...

> > How we can differentiate the following situation: ... > > That's actually a valid point. Having given it some thought, I think we should not allow any tests...

@WildH0g you seem pretty busy. I have some time and I added new functionality for testing not just the error message but also the error type. The name of the...

@WildH0g I have time during the weekend to make the changes I mentioned: Corrected my previous version. Now`catchErr` extending its signature using default input arguments, can also test error message...

Hi @WildH0g Added the following changes in the version I uploaded today. I don't envision any other future changes from my end. IMHO now we have something more solid from...