Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

We currently have Gen.forAll { it == true }. If we want to invert it, it's ok to write Gen.forAll { !(it == true) } .

It would be syntactically pleasant to write Gen.forNone instead, like:

test("Random string shouldn't be a valid email") {
     Arb.string().forNone { it.isEmail() }` 
}

vs

test("Random string shouldn't be a valid email") {
    Arb.string().forAll

Code lens in vscode cannot run tests when TestCases are provided because we are using the opening brace position as the line filter, but test cases will move it further down, not matching the filter. To avoid difficult parsing let's change that to using $MyInvocation.ScriptLineNumber instead of $ScriptBlock.StartPosition.StartLine, which will give us the position of the It (and other) co

Summary

ShouldContainOnly is used in a few places where we know what kind of elements we are dealing with, in this case instead of using the term element we could use a more descriptive name.

Example

Spliterator<?> actual = createSpliterator(SORTED | ORDERED);
spliterators.assertHasOnlyCharacteristics(INFO, actual, DISTINCT, SORTED);

fails with this error

Feature Request

Description:
API for Date matchers. Some matchers are inspired by Jasmine Matchers.

Possible solution:

Jasmine-like matchers:

expect(date).toBeDate(); // Matcher added
expect(date).toBeValidDate();  // Matcher added

expect(date).toBeAfter(otherDate); // Matcher added
expect(date).toBeBefore(otherDa

As a SDET
I want a documentation or Wiki page where the expected vs actual field matching is explained
So that I can use these in my test automation to test the server response payloads and headers
e.g. id=123 , id="123", isValid=true, isValid="true" etc

AC1:

Cover the following currently supported mechanisms with examples

• $EQ
• (int)
• (float) or (decimal)
• (boolean)

Normally, the "to be truthy" assertion does not take any value as it simply asserts that a subject can be coerced to a boolean true (in the case of "to be falsy" it is coercion to boolean false).

It seems that early on these assertions inherited an optional form where a custom message can be supplied as their argument - this was likely inspired by earlier assertions frameworks (assert on node

Platform (jvm, js, android): jvm
Extension (none, kotlin 1.3, jdk8): jdk8

Code related feature

expect(ZonedDateTime.now()).isAfter("2020-04-28T12:00Z")

//instead of

expect(ZonedDateTime.now()).isAfter(ZonedDateTime.of(2020,4,28,12,0,0,0, ZoneId.of("Z")))

Following the things you need to do:

atrium-logic:

• duplicate each method in chronoZonedDateTimeAsserti

Is your feature request related to a problem? Please describe.

Currently the built-in Check methods relating to the comparison operators <, >, ==, etc. are sort of long and unwieldy (the rationale here was to make it human-readable). However, it seems like pandas and indeed python uses shorthand of ge (>=), le (<=), etc. for these binary operators.

**Describe the soluti