E2E: Update the way selecting a future date for schedulePost

[htdat]

Fix #652

Description

The root cause is described here #652 (comment)

To fix this issue, I am changing the way selecting a future date for schedulePost:

• Calculate the date in 2 weeks since today.
• Use DOM selector and update the respective values for day, month, year.

Some notes:

• I researched how Gutenberg approaches this issue and at the moment, there is no support for creating schedule posts in package e2e-test-utils. I pulled Gutenberg and searched on this specific folder packages/e2e-test-utils/src, which hosts this package.
• Instead, here is how a similar issue (updating date and time of a post) is handled in Gutenberg. That's basically the same method I am using here https://github.com/WordPress/gutenberg/pull/27558/files#diff-3836a6db831ccfe3af87b4c80a7fa67c44eb8d4239cff2dbfe3025924cd4e991R78-R79
• We can not set a date too far in the future as it will not display when viewing wp-admin/index.php?page=calendar by default.

Steps to Test

• Check out this PR.
• Run E2E tests and verify the issue in E2E test - calendar-body.test.js #652 is no longer.

If possible, we can use the diff in this comment #652 (comment) to generate new screenshots with this fix.

With this fix, the date of the post is expected now:

• schedulePost_before-choosing-date: date is today - June 09.
• schedulePost_after-choosing-date: date is the date after 14 days: June 23.
• calendar_before-drag-drop: date is show the expected scheduled post date: June 23
• calendar_after-drag-drop: after the drag and drop, it is moved up to June 16.

[htdat]

In case, it helps, here is my screen record for the specific failed test with this fix:

https://d.pr/v/kWnVMx

[nielslange]

LGTM!

I tested this PR using the following steps:

1. Start Docker
2. Run npm run wp-env start
3. Run npm run test-e2e
4. One test case is failing

> edit-flow@2.0.0 test-e2e
> wp-scripts test-e2e --config tests/e2e/jest.config.js

 FAIL  tests/e2e/specs/calendar-body.test.js (25.717s)
  ● Calendar Body › expects a scheduled post can be dragged and dropped

    expect(received).not.toContain(expected) // indexOf

    Expected value: not "Scheduled Post"
    Received array:     ["Scheduled Post", "Published Post"]

      94 |         expect(await scheduledPostDay.evaluate((node) => {
      95 |             return Array.prototype.slice.call(node.querySelectorAll('.item-headline.post-title strong')).map((n) => n.innerText)
    > 96 |         })).not.toContain('Scheduled Post');
         |                 ^
      97 |     });
      98 | });

      at _callee3$ (specs/calendar-body.test.js:96:17)
      at asyncGeneratorStep (specs/calendar-body.test.js:7:103)
      at _next (specs/calendar-body.test.js:9:194)
          at runMicrotasks (<anonymous>)
      at processTicksAndRejections (../../node:internal/process/task_queues:96:5)

 PASS  tests/e2e/specs/editorial-comments.test.js (7.023s)
 PASS  tests/e2e/specs/calendar-header.test.js (5.558s)
 PASS  tests/e2e/specs/simple.test.js

Test Suites: 1 failed, 3 passed, 4 total
Tests:       1 failed, 5 passed, 6 total
Snapshots:   0 total
Time:        39.61s, estimated 40s
Ran all test suites.

5. Check out this PR
6. Run npm run test-e2e
7. All test cases are successful

> edit-flow@2.0.0 test-e2e
> wp-scripts test-e2e --config tests/e2e/jest.config.js

 PASS  tests/e2e/specs/calendar-body.test.js (25.829s)
 PASS  tests/e2e/specs/calendar-header.test.js (5.989s)
 PASS  tests/e2e/specs/simple.test.js
 PASS  tests/e2e/specs/editorial-comments.test.js (6.472s)

Test Suites: 4 passed, 4 total
Tests:       6 passed, 6 total
Snapshots:   0 total
Time:        39.641s
Ran all test suites.

[mikeyarce]

Looks good to me! I just had a small nitpick about one of the comments.

Thanks @htdat - so nice to see that green checkmark next to all the tests!

[htdat]

Thanks @nielslange and @mikeyarce! I've merged this PR after updating the comment :D