Core: strict vs not strict inequalities in Assertions

[annappropriate]

Part of my simulation definition is assertions(global.failedRequests.percent.lessThan(100))
Gatling output:

---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                            0 (  0%)
> 800 ms < t < 1200 ms                                  0 (  0%)
> t > 1200 ms                                           0 (  0%)
> failed                                               60 (100%)
    <some output skipped>
Global: percentage of failed requests is less than 100 : true

This seems a bit misleading (especially the last line), I wonder if lessThan and greaterThan should be strict inequalities and API should also provide lessThanOrEqual and greaterThanOrEqual or something like that?
Documentation does not say anything about strictness either.

[slandelle]

I agree.

This can only go in 2.3, as it would be an API breakage (even if it's for the better).
Would you be interested in contributing?

[annappropriate]

Yes, I'd absolutely love to contribute.

[slandelle]

• Let's drop greaterThan and lowerThan
• Introduce gt, gte, lt, lte
• Add optional parameters on between with default value to exclude bounds