Current behavior

Hello, I would simply like to request that the documentation for find() (https://enzymejs.github.io/enzyme/docs/api/ShallowWrapper/find.html) be updated to reflect its snapshot-nature. For example, in a situation where clicking a button updates state under the hood...

   // some set up code goes here. 

    const deleteButton = wrapper.find('[data-enzyme-id

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,

I have a feeling that most people use async/await in new code, and none of the examples use it.

Also, from browsing random issues, better tests will be written using this structure. For example #543 is caused by not using async/await in tests.

// This passes!
it("should reset", async () => {
        request(app)
            .get("/reset")
            .expect(205);
});

The documentation for .above states:

The aliases .gt and .greaterThan can be used interchangeably with .above.

However, for .least:

The alias .gte can be used interchangeably with .least.

To my mind, there should be a .greaterThanOrEqual alias for .least in addition to

refer: microsoft/vscode#27950 (comment)

cc @kirksl

note that today you can do things like print foo in the debug terminal input / REPL as a workaround

Hi,

first of all, I really like Kotest's matchers and consider to move from AssertJ to them.

But I noticed that AssertJ adds useful line breaks after each element in the failure message of the collection matches. Here is an example:

AssertJ:

assertThat(actualDesigns).containsExactly(
    Design(id = 1, userId = 9, name = "Cat", dateCreated = Instant.ofEpochSecond(151827819

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

Description

When comparing two identical dictionaries which use an object as the key, .Should().BeEquivalentTo() fails.

If I override .Equals() then it succeeds, which feels like it goes against the principle of equivalence expectations.

Whilst this may be my misunderstanding of the expectation, the docs don't seem to call this limitation out, so perhaps worth documenting if deemed

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

Hi,

Sometimes I want to capture the request and response traffic details, in which case I need to set proxy and use Charles. In net/http, we can set the HTTP_PROXY environment variable to achieve this goal, however this does not work in httpexpect.

Is there any way we can proxy httpexpect's traffic?

Thanks.

Describe the feature you'd like:

Jest-Extended has an assertion named the same as jest-extended's one:

-> https://github.com/jest-community/jest-extended#tobeempty
-> https://github.com/testing-library/jest-dom#tobeempty

When both libs are used in the same project, in my case the version of jest-extended overwrites the one from jest-dom. But this might vary depending on the order use

It would be nice if this worked:

const a = foo();
const b = bar();

// Both `a` and `b` is an `object`, but TS only knows they're `any`.

if (is.all(is.object, a, b)) {
	// `a` and

From twitter:
https://twitter.com/bbrannic/status/1077892960426041344

The following repo has a good reporting solution which expects the test-run results in JSON format
https://github.com/damianszczepanik/cucumber-reporting

Zerocode already produces test-run results in JSON format.
Some subset of data from this is used for CSV reporting and some for HTML reporting.

Currently it uses _e

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

Easy fix:

self.fd:write(string.format(' <testcase classname="%s" name="%s" time="%0.3f">\n', node.className, node.testName, node.duration ) )
becomes
self.fd:write(string.format(' <testcase classname="%s" name="%s" time="%0.3f">\n', xmlEscape(node.className), xmlEscape(node.testName), node.duration ) )

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

Example:

$pattern = "sign/in";
$actual = "https://test.dev/sign/in?_fid=j3o0";
\Tester\Assert::match($pattern, $actual);

Current tester output:

Failed: 'https://test.dev/sign/in?_fid=j3o0' should match
       ... 'sign/in' in testAbc()

It would nice something like:

Failed: 'wrong pattern format given.'
Failed: 'https://test.dev/sign/in?_fid=j3o0' should matc

With redux-things/redux-actions-assertions-js#3 "with state" function now supports function.
Docs needed to be updated:

• chai
  • Update function definition
  • Add example of usage
• expect
  • Update function definition
  • Add example of usage
• expect.js
  • Update function definition
  • Add example of usage
• should
  • Upd

Currently, the SeriesSchema object doesn't validate the index of the schema. The purpose of this task is to extend the __init__ signature of SeriesSchema to take an index argument, which would take a pa.Index or pa.MultiIndex. In the validate / __call__ call, the index should be checked.