Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document recommended testing strategy for the new platform plugins #53135

Closed
4 of 5 tasks
mshustov opened this issue Dec 16, 2019 · 3 comments · Fixed by #57587
Closed
4 of 5 tasks

Document recommended testing strategy for the new platform plugins #53135

mshustov opened this issue Dec 16, 2019 · 3 comments · Fixed by #57587
Assignees
@rudolf @pgayvallet @joshdover
Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mshustov
Copy link
Contributor

mshustov commented Dec 16, 2019 •
edited by joshdover
Loading

The platform team should provide recommendations regarding testing on the new platform:

  • plugin contracts. Plugin contract is a plugin public API and abides by Kibana server policy. Thus backward compatibility becomes paramount.
  • new platform compatibility. The new platform, especially in the browser, introduced a lot of new concepts: lifecycles, long-lived SPA sessions, multiple runtime plugins. It means that LP plugins don't have tests for any of them. The solution team required adding new test cases as a part of the migration effort.

Are there any general Kibana specific recommendations about testing? Say how to apply the testing pyramid to the Elastic Stack? It can be worth discussing with other solution teams.

Areas to be filled in in the testing doc:
@mshustov mshustov added blocker Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Dec 16, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@joshdover joshdover self-assigned this Dec 17, 2019
@joshdover joshdover mentioned this issue Dec 18, 2019
Merged
10 tasks
@joshdover joshdover changed the title Document recommended testing strategy for the new plartform plugins Document recommended testing strategy for the new platform plugins Jan 13, 2020
@joshdover
Copy link
Contributor

The initial PR has been merged with a basic outline of the doc. I'll delegate each area that needs to be filled in this week.

@mshustov
Copy link
Contributor Author

Working on http route testing

@mshustov mshustov mentioned this issue Jan 15, 2020
Merged
@pgayvallet pgayvallet mentioned this issue Jan 29, 2020
Merged
@joshdover joshdover mentioned this issue Feb 13, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rudolf rudolf

@pgayvallet pgayvallet

@joshdover joshdover

Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[skip-ci] Remove plugin contracts header from TESTING.md joshdover/kibana
5 participants
@rudolf @pgayvallet @joshdover @mshustov @elasticmachine