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,

It would be nice to start building Pester on PowerShell 7 as well to see if it is compatible and keep it that way. To achieve that we need to research on which build servers v7 is already available. Right now we are building on TravisCI (Linux and MacOS), on AppVeyor (PowerShell 4+) and AzureDevOps (PowerShell 2&3).

Not sure if the build task needs to run on all three platforms, but it would be

https://github.com/assertj/assertj-core/blob/f27b022a369ba731ed72413f6c10c82a9e539495/src/main/java/org/assertj/core/internal/Maps.java#L745
The call mentioned in the link fails with IllegalArgumentException if entries is empty, and actual is not. This, however, would work if actual is empty as well (the mentioned line is not executed in this case). Thus, execution success depends on `actua

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

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

Currently, the MultiIndex schema component str representation is the same as
the DataFrameSchema representation

Describe the solution you'd like

the MultiIndex schema component should implement its own str representation
so that it doesn't render columns and instead shoulds the indexes.

why steps in zerocode-junit-interactive-fuzzy-search.html report are not displayed in order as they are in the json scenarios file
For example:
My scenarios in json file, I defined below steps:

{
  "scenarioName": "Add Clusters: GIVEN- environment variables endpoint, WHEN- I invoke POST request, I will be able to add/update cluster for my environment",
  "ignoreStepFailures": false,
  "

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

Code related feature

expect(path).toBeAnEmptyDirectory()

//instead of

expect(path)
  .toBeADirectory()
  .feature("findFirstFile", { Files.list(this).use { it.findFirst() } }) {
    isEmpty()
  }

Following the things you need to do:

logic

• extend PathAssertions with a function `toBeEmptyDi

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