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

Improve usability/documentation of Gaia e2e tests #2902

Closed
1 of 3 tasks
Tracked by #2406
p-offtermatt opened this issue Jan 23, 2024 · 1 comment
Closed
1 of 3 tasks
Tracked by #2406

Improve usability/documentation of Gaia e2e tests #2902

p-offtermatt opened this issue Jan 23, 2024 · 1 comment
Assignees
@MSalopek
Labels
admin: epic An EPIC -- meta issue used to track a body of work S: Productivity Productivity: Developer tooling, infrastructure improvements enabling future growth scope: docs Improvements or additions to documentation scope: testing Code review, testing, making sure the code is following the specification.

Comments

@p-offtermatt
Copy link
Contributor

p-offtermatt commented Jan 23, 2024 •
edited
Loading

Problem

We want to improve the usability of the Gaia e2e tests. This concerns mostly the documentation around the e2e tests, but if there are easy things we can change/refactor/add to improve the tests, we should be aware of those and consider doing them, too.

Closing criteria

We have more confidence in the Gaia e2e tests,
and it is easier to onboard onto them.

Problem details

The problems we seem to have with the Gaia e2e tests currently are:

  1. it is not easy to find out what is being tested or not
  2. it is hard to onboard onto the e2e tests
  3. some things are tested by Hypha very late in the process (e.g. upgrades),
    even though it might be possible to test them earlier and fail sooner rather than later.

Task list

Must have
Preview Give feedback
  1. Add more documentation for e2e tests on Gaia #2903
    S: Productivity scope: docs scope: testing
    MSalopek

Nice to have
Preview Give feedback
@p-offtermatt p-offtermatt added admin: epic An EPIC -- meta issue used to track a body of work status: waiting-triage This issue/PR has not yet been triaged by the team. labels Jan 23, 2024
@github-project-automation github-project-automation bot moved this to 🩹 F1: Triage in Cosmos Hub Jan 23, 2024
@p-offtermatt p-offtermatt added scope: testing Code review, testing, making sure the code is following the specification. S: Productivity Productivity: Developer tooling, infrastructure improvements enabling future growth and removed status: waiting-triage This issue/PR has not yet been triaged by the team. labels Jan 23, 2024
@p-offtermatt p-offtermatt moved this from 🩹 F1: Triage to 📥 F2: Todo in Cosmos Hub Jan 23, 2024
@p-offtermatt p-offtermatt mentioned this issue Jan 23, 2024
Closed
@mpoke mpoke added the scope: docs Improvements or additions to documentation label Apr 4, 2024
@mpoke
Copy link
Contributor

mpoke commented Apr 4, 2024

Closing this in favor of #2903

@mpoke mpoke closed this as completed Apr 4, 2024
@github-project-automation github-project-automation bot moved this from 📥 F2: Todo to 👍 F4: Assessment in Cosmos Hub Apr 4, 2024
@mpoke mpoke moved this from 👍 F4: Assessment to ✅ Done in Cosmos Hub Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MSalopek MSalopek

Labels
admin: epic An EPIC -- meta issue used to track a body of work S: Productivity Productivity: Developer tooling, infrastructure improvements enabling future growth scope: docs Improvements or additions to documentation scope: testing Code review, testing, making sure the code is following the specification.
Projects
Cosmos Hub
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mpoke @MSalopek @p-offtermatt