You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: test.step/it.step (like in playwright) for the integrated tests (with @testing-library/react, for example) #16027
In complex functional tests (to test react+redux+saga) in complex, it is very convenient to make a sequence of steps in the test, like a playwright
Motivation
I would like to see a more precise test structure in the reports.
Example
At the moment the test looks like this:
describe('Test select nodes on scheme canvas',()=>{it('Select RED node',async()=>{const{ screen, store }=awaitinitWebview();// Add RED nodeawaitscreen.scheme.toolbar.buttonAddRedNode.click();awaitexpect(store.getNode('node-1)).toBeExisted();
awaitexpect(screen.scheme.canvas.getNode('node-1')).toBeVisible();// Select RED nodeawaitscreen.scheme.scheme.getNode('node-1').click();awaitexpect(store.getSelectedNode()).toEqual('node-1');awaitexpect(screen.scheme.canvas.getNode('node-1')).toBeSelected();});});
Wanna:
describe('Test select nodes on scheme canvas',()=>{it('Select RED node',async()=>{const{ screen, store }=awaitintitWebview();awaitit.step('Add RED node',async()=>{awaitscreen.scheme.toolbar.buttonAddRedNode.click();awaitexpect(store.getNode('node-1')).toBeExisted();awaitexpect(screen.scheme.canvas.getNode('node-1')).toBeVisible();});awaitit.step('Select RED node',async()=>{awaitscreen.scheme.scheme.getNode('node-1').click();awaitexpect(store.getSelectedNode()).toEqual('node-1');awaitexpect(screen.scheme.canvas.getNode('node-1')).toBeSelected();});});});
Pitch
This pattern would seemingly work in both async and sync test blocks and would allow us to have more flexibility with writing out tests while still getting clear indication on what step a test failed on.
I'd like to take this one ([Feature]: test.step/it.step (like in playwright) for the in). I'll look into the root cause and follow up with a PR. (claiming via @LeonxLJX)
I'd like to take this one ([Feature]: test.step/it.step (like in playwright) for the in). I'll look into the root cause and follow up with a PR. (claiming via @LeonxLJX)
Hi @LeonxLJX, just checking in on this one — are you still actively working on it? I noticed PR #16157 has been stale for a while (unresolved merge conflicts, missing CLA, and a few failing checks), so I wanted to see if you have a WIP branch somewhere before I look into picking it up myself. No rush, just want to avoid duplicate work 🙂
Since there's been no update, I'll go ahead and start working on this. Will link a PR here once I have something ready — happy to coordinate if you're still planning to work on it too, @LeonxLJX.
Activity
github-actions commentedon May 2, 2026
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.
ahnpnl commentedon May 7, 2026
not stale
SimenB commentedon May 7, 2026
Happy to take a PR for this 🙂 If anybody picks this up there's no need to add support in
jest-jasmine-jest-circusis enough.LeonxLJX commentedon Sep 1, 2026
I'd like to take this one (
[Feature]: test.step/it.step (like in playwright) for the in). I'll look into the root cause and follow up with a PR. (claiming via @LeonxLJX)LeonxLJX commentedon Sep 1, 2026
I'd like to take this one (
[Feature]: test.step/it.step (like in playwright) for the in). I'll look into the root cause and follow up with a PR. (claiming via @LeonxLJX)drewnetic commentedon Sep 16, 2026
Hi @LeonxLJX, just checking in on this one — are you still actively working on it? I noticed PR #16157 has been stale for a while (unresolved merge conflicts, missing CLA, and a few failing checks), so I wanted to see if you have a WIP branch somewhere before I look into picking it up myself. No rush, just want to avoid duplicate work 🙂
drewnetic commentedon Sep 26, 2026
Since there's been no update, I'll go ahead and start working on this. Will link a PR here once I have something ready — happy to coordinate if you're still planning to work on it too, @LeonxLJX.