Add skills for FTR & Scout testing

[tylersmalley]

null

[elasticmachine]

⏳ Build in-progress, with failures

• Buildkite Build
• Commit: 73b2f41

Failed CI Steps

• Check changes in Saved Objects

[dmlemeshko]

Since in FTR it block often servers as an intermediate step role, migration might not be that straight forward:

• it block represents only partial step: convert it => into test.step under describe.test/test
• it block represents complete test case: it => describe/it -> test.describe/test

FTR:

  describe('FTR test suite', function () {
    before(async () => {
    });

    after(async () => {
    });

    it('go to app and take action 1, async () => {
       // default layout check, click few buttons to create some entity
    });

    it('take actions 2 & 3', async () => {
       // we are in the same browser context, continue...
       // fill in form, press submit, check entity is created
    });

    it("remove entity", async () => {
       // we are in the same browser context, continue...
       // different test case, deserves its own independent test block
    });
  });

Scout:

  test.describe('FTR test suite', { tag: ['@ess'] }, () => {
    test.beforeAll(async ({ apiServices }) => {
    });

    test.afterAll(async ({ apiServices }) => {
    });

    test('create entity', async () => {
       // fresh browser context
       test.step(...)
       test.step(...)
       test.step(...)
    });

    test('delete entity', async () => {
       // fresh browser context
       test.step(...)
       test.step(...)
    });
  });

[csr]

This file will have to be updated with our official AppEx QA guidance (issue here: https://github.com/elastic/appex-qa-team/issues/638).

[dmlemeshko]

Could it be useful to mention that FTR configs can be "executable" and "read-only": checking .buildkite/ftr_*_configs.yml files for config listing under enabled/disabled sections helps to confirm the config is the executable.

[csr]

A strong start, and a good iteration. We'll be iterating this once more once we experiment with them further. Thanks!

[kibanamachine]

Starting backport for target branches: 8.19, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/22167467434

[kibanamachine]

Starting backport for target branches: 8.19, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/22167467579

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - Adds initial agents.md file (#250833)
❌	9.2	Backport failed because of merge conflicts
❌	9.3	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 251386

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - Adds initial agents.md file (#250833)
❌	9.2	Backport failed because of merge conflicts
❌	9.3	Backport failed because of merge conflicts You might need to backport the following PRs to 9.3: - [Dashboards as code] Add conversion functions from/to API filters interface and stored filters (#242043) - Relocate @kbn/timelines-plugin (#250597)

Manual backport

To create the backport manually run:

node scripts/backport --pr 251386

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251386 locally
cc: @tylersmalley

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251386 locally
cc: @tylersmalley

[tylersmalley]

💚 All backports created successfully

Status	Branch	Result
✅	9.3
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @tylersmalley

[kibanamachine]

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @tylersmalley

[kibanamachine]

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
cc: @tylersmalley

[tylersmalley]

💚 All backports created successfully

Status	Branch	Result
✅	9.2

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation