Bug: Codeception tests are failing because of rendering issue in the headless browser

[mikelittle]

The codeception tests for Audit trail are failing because of rendering issue in the headless browser. The button to publish is being overlapped by the sidebar. Codeception could not publish the test post.

Steps to reproduce:

1. Run the codeception tests for altiis/security composer dev-tools codecept -p packages/security/tests/ run
2. Observe that the tests fail.

Note the second test fails because the first one did.

I expect all the tests to pass.

The test output:

1) AuditLogCest: Test create post for audit log
 Test  ../packages/security/tests/acceptance/AuditLogCest.php:testCreatePostForAuditLog

  [Facebook\WebDriver\Exception\ElementClickInterceptedException] Element <button class="components-button editor-post-publish-button editor-post-publish-button__button is-primary is-compact" type="button"> is not clickable at point (1835,96) because another element <div class="components-panel__header interface-complementary-area-header editor-sidebar__panel-tabs"> obscures it

Here is the screenshot the testing rig saves.

Note, the Publish button is obscured by the sidebar.

I also tried it using Firefox, with the same result:

Also note, by default the tests run on a simulated 800x600 screen, which I initially thought was the cause for the sidebar to render over the button. But changing to run at 1080p (as in the screenshots) still gave the same results.

Acceptance criteria:

• Verify source of bug
  • Gutenberg
  • Statistics consent popup that renders even on the block editor page. This may mess up the rendering in the headless browser.
  • Headless Browser
• The codeception tests should complete successfully.

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

• Is the title clear?
• Is the description clear and detailed enough?
• Are acceptance criteria listed?
• Have any dependencies been identified? (Optional)
• Have any documentation/playbook changes been identified? (Optional)
• Is an estimate or time box assigned?
• Is a priority label assigned?
• Is this ticket added to a milestone?
• Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

• Has the acceptance criteria been met?
• Is the documentation updated (including README)?
• Do any code/documentation changes meet project standards?
• Are automatic tests in place to verify the fix or new functionality?
  • Or are manual tests documented (at least on this ticket)?
• Are any Playbook/Handbook pages updated?
• Has a new module release (patch/minor) been created/scheduled?
• Have the appropriate backport labels been added to the PR?
• Is there a roll-out (and roll-back) plan if required?

[mikelittle]

This rendering issue may be caused by the statistics consent popup that renders even on the block editor page. Potentially, this may mess up the rendering in the headless browser

This is the original bug raised about the consent popup humanmade/altis-core#456

[jerico]

Hey team! Please add your planning poker estimate with Zenhub @wisyhambolu @ferschubert-hm @mikelittle