Changes related to the issues #61 and #62 plus 2 new build parameters to control the success conditions in CI tools

[eSh3m4]

First I kept robymathew/ApexUnit@12fc46c solution of the issue #62 and #61 over mine and merged it with the solution of similar ones provided in the 2.6.8 release.

Then I solved the reporting issues introduced by those fixes as the computations where chunked in several calls and batches but not reconciled when having more than 200 tests (2075 tests methods in my case 🥇).

Finally I have added a time based report directory and two new optional parameters to fine tune the build outcomes when the scripts are in a Continuous integration cycle when for instance you are only interested in the reports but don't want to block the build chain.

//TODO : parametrize the time based report directory in order to keep the evolution seamless for current users

[robymathew]

HI - any update on this? These fixes would allow my team to move off our personal fork and back onto the main repo

[vamshi-sfdc]

@eSh3m4 can you please resolve the conflicts and have your changes pass the travis CI?

I have assigned @dragon0556 to help you with code review

[dragon0556]

@eSh3m4 Can you please work on conflicts. It seems that, you have old .travis.yml file. Due to this travis CI is failing. It would be great if you merge latest master into your branch and remove the conflicts.

[salesforce-cla[bot]]

Thanks for the contribution! Before we can merge this, we need @eSh3m4 to sign the Salesforce.com Contributor License Agreement.

[eSh3m4]

Hi - Not quite sure of the direction regarding build results, I am reopening the PR and let you decide :) Thank you all for this powerful tool!

[salesforce-cla[bot]]

Thanks for the contribution! Before we can merge this, we need @EricShema @code-sagar to sign the Salesforce.com Contributor License Agreement.

[salesforce-cla[bot]]

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Rutuja Chaudhari r***@r***.i***.s***.com. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, sign the Salesforce.com Contributor License Agreement and this Pull Request will be revalidated.

[salesforce-cla[bot]]

Thanks for the contribution! Before we can merge this, we need @code-sagar to sign the Salesforce.com Contributor License Agreement.