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 already have them for collections

Description

When trying to assert that an interface type has internal access, the following assertion message is thrown:

Expected expression to be Internal, but it is InvalidForCSharp.

Complete minimal example reproducing the issue

Assuming the following definition exists in the scope of the test:

internal interface ITest {}

The following demonstrate

Summary

Similar to assertj/assertj-core#2401 but for flatExtracting/flatMap.

There are quite a few variations to cover and tests;

• flatExtracting(Function), flatMap(Function) , flatExtracting(ThrowingExtractor) and flatMap(ThrowingExtractor), will be fixed by changing doFlatExtracting, tests needed for the 4 methods exposed in the API.
• [

Let's dive into the source code:

https://github.com/sindresorhus/is/blob/d528545e02de3396ea900cd93af478292f0697ee/source/index.ts#L184

Only [Symbol.iterator] property is checked, meaning the value is at least Iterable<T>. It may be IterableIterator<T> if the presence of one more property, next, is ensured.

interface Iterable<T> {
    [Symbol.iterator](): Iterator<T>;
}

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

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