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,

Just like Json Matchers, we should have Yaml Matchers, too. While I'm aware that kotlinx.serialization has no built-in support for YAML, there is the multi-platform https://github.com/him188/yamlkt add-on for kotlinx.serialization which we could probably use.

Before you file a bug, have you:

• Tried upgrading to newest version of Fluent Assertions, to see if your issue has already been resolved and released?
• Checked existing open and closed issues, to see if the issue has already been reported?
• Tried reproducing your problem in a new isolated proje

Using the existing matches(Pattern) and POSIX regex character classes, we can add specialized assertions to AbstractCharSequenceAssert.

assertThat(string).isAlphabetic();   // \p{Alpha}
assertThat(string).isAlphanumeric(); // \p{Alnum}
assertThat(string).isASCII();        // \p{ASCII}
assertThat(string).isDigit();        // \p{Digit}
assertThat(string).isHexadecimal();  // \p{X

Describe the bug
pa.errors.SchemaErrors.failure_cases only returns the first 10 failure_cases

• I have checked that this issue has not already been reported.
• I have confirmed this bug exists on the latest version of pandera. 0.6.5
• (optional) I have confirmed this bug exists on the master branch of pandera.

Note: Please read [this guide](https://matthewrocklin.c

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)

Static functions from the JUnit 5 Assertions class don't seem to be diagramed. Add some unit tests for static functions to make sure they work correctly. And fix any bugs found.

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

Code related feature

We also want to provide samples for the infix api

Following the things you need to do:

• copy SequenceSubjectChangerSamples from fluent-api to api-infix, adjust imports ...api.fluent... to ...api.infix... and adjust the samples accordingly (always use the infix syntax, never the fl

While working on a fix for frankban/quicktest#125 it appeared that there could be an opportunity for improving the Not(Checker) error message for standard checkers, such as Equals, IsTrue etc.

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