Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

[Fleet] Add upgrade of Elastic stack test to e2e-testing capabilities #821

Closed
EricDavisX opened this issue Mar 1, 2021 · 2 comments
Closed
Labels
Team:Fleet Label for the Fleet team

Comments

@EricDavisX
Copy link
Contributor

First step is to have a harness here in e2e-testing to cite a 'source' or "stale" build version of stack, and then perform an install and some setup steps (some tests we already have written!) and then cite a 'upgrade-to' version to upgrade the stack to after which time we can run more tests and do specific validations.

some commentary about how upgrade tests (as seen by the test of the Agent upgrade feature) may be challenging to do during CI, so it must remain a nightly-only feature and citation for now
#652
#671

some commentary / pr on how we did the Agent upgrade feature:
#506

  • just for inspiration, not that the upgrade of the Agent or the stack are terribly similar.
@EricDavisX EricDavisX added the Team:Fleet Label for the Fleet team label Mar 1, 2021
@EricDavisX
Copy link
Contributor Author

@ph @mdelapenya @kevinlog just fyi. Separate effort from the custom stand-alone upgr8er tool.

@kseniia-kolpakova
Copy link

It will be covered in #1133
@EricDavisX please reopen if you have concerns

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Team:Fleet Label for the Fleet team
Projects
None yet
Development

No branches or pull requests

2 participants