test(Transition): more test transition

[underfin]

No description provided.

[underfin]

When I add transiton test.It always fail down in me local dev.So its is slow with add test. and it lead me to confused with diff the behavior with v2.So I want to get some help to improve it.

other.
When test the dom element with spy called argments.I get "{}".
When I get use page().evalate(()=> document.getelementbyid()),sometime is "{}", sometimes is "{_leavecb:{}}", or anther similar something.
I want to get some suitable suggestion to relsove this.
My idea is only check it is equal and ignore other property.

[yyx990803]

The reason your tests were failing inconsistently is because we are testing by talking to Puppeteer so everything is async and may or may not be longer than the actual microtask inside Puppeteer. So when you await click('button'), the microtask may have already fired so you won't be able get the transition start state.

The way to fix that is by running the whole click -> wait for microtask tick -> get transition start classname procedures directly inside the Puppeteer browser by using page().evaluate. This guarantees consistent results.

Another thing is the nextFrame you were using is using the JSDOM requestAnimationFrame, which is not actually the requestAnimationFrame in the Puppeteer browser.

[yyx990803]

See 9d111f5 for the fixed version.

[underfin]

Todo:
1.some test has bugs and I will commit pr and update test
2.test hooks called with arguments and transition element class state.I don't have correct solution. And this need your some help.

[underfin]

It's here.Should test hooks arguments.It will be meet error when i use expect(beforeLeaveSpy).toBeCalledWith(await page().evaluate(() => // get dom)).I don't has right way.