Interactivity API: Added comments for directive parsing #103407
Annotations
10 errors and 1 notice
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
Run the tests:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
Run the tests:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
Run the tests:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
Run the tests:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
Run the tests:
test/e2e/specs/interactivity/router-navigate.spec.ts#L115
4) [chromium] › interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
- locator resolved to <output data-testid="router navigations pending" data-wp…></output>
- unexpected value ""
113 | const title = page.getByTestId( 'title' );
114 |
> 115 | await expect( navigations ).toHaveText( '0' );
| ^
116 | await expect( status ).toHaveText( 'idle' );
117 |
118 | const resolvers: Function[] = [];
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:115:31
|
|
Run the tests
27 failed
[chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
[chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
[chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
[chromium] › interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment
[chromium] › interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends
[chromium] › interactivity/router-navigate.spec.ts:191:6 › Router navigate › should force a page reload when the `clientNavigationDisabled` config is set to true
[chromium] › interactivity/router-navigate.spec.ts:214:6 › Router navigate › should overwrite the state with the one serialized in the new page
[chromium] › interactivity/router-navigate.spec.ts:242:6 › Router navigate › should not try to overwrite getters with values from the initial data
[chromium] › interactivity/router-navigate.spec.ts:270:6 › Router navigate › should force a page reload when navigating to a page with `clientNavigationDisabled`
[chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated
[chromium] › interactivity/router-regions.spec.ts:40:6 › Router regions › should update after navigation
[chromium] › interactivity/router-regions.spec.ts:58:6 › Router regions › should preserve state across pages
[chromium] › interactivity/router-regions.spec.ts:74:6 › Router regions › should preserve context across pages
[chromium] › interactivity/router-regions.spec.ts:90:6 › Router regions › can be nested ────────
[chromium] › interactivity/router-regions.spec.ts:101:6 › Router regions › Page title is updated 2
[chromium] › interactivity/store.spec.ts:21:6 › store › non-plain objects are not proxified ────
[chromium] › interactivity/store.spec.ts:26:6 › store › Ensures that state cannot be set to a non-object
[chromium] › interactivity/tovdom-islands.spec.ts:26:6 › toVdom - islands › directives that are inside islands with json objects should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:33:6 › toVdom - islands › directives that are inside islands with strings should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:49:6 › toVdom - islands › directives inside islands should not be hydrated twice
[chromium] › interactivity/tovdom-islands.spec.ts:57:6 › toVdom - islands › islands inside inner blocks of isolated islands should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:66:6 › toVdom - islands › islands should recover their namespace if an inner island has changed it
[chromium] › interactivity/with-scope.spec.ts:19:6 › withScope › directives using withScope should work with async and sync functions
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit)
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:268:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@WebKit)
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions
194 passed (21.6m)
|
The logs for this run have expired and are no longer available.
Loading