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.

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

Add e2e tests to verify that basic CRUD operations are working #4700

Closed
akhenry opened this issue Jan 10, 2022 · 1 comment
Closed

Add e2e tests to verify that basic CRUD operations are working #4700

akhenry opened this issue Jan 10, 2022 · 1 comment
Labels
needs:e2e Needs an e2e test source:community Community contribution or request type:enhancement

Comments

@akhenry
Copy link
Contributor

akhenry commented Jan 10, 2022

Is your feature request related to a problem? Please describe.
We need some e2e tests to perform automated "smoke" tests to verify that the basic operations of the application are working. This issue focuses on testing that basic CRUD operations on objects are working ok. A separate issue exists to test telemetry display.

Describe the solution you'd like
This task is to verify that:

  • New objects can be created (a test already exists for this)
  • Existing objects can be navigated to
  • Existing objects can be mutated
  • Objects can be deleted from their parent's composition.

This probably necessitates the use of LocalStorage in order to verify mutation. This will require LocalStorage to be initialized into some known state at the start of the tests before RUD operations can be carried out.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@unlikelyzero unlikelyzero added the needs:e2e Needs an e2e test label Jan 10, 2022
@unlikelyzero unlikelyzero added this to To triage in Improve Test Coverage via automation Jan 10, 2022
@unlikelyzero unlikelyzero moved this from To triage to Ready! in Improve Test Coverage Mar 9, 2022
@unlikelyzero unlikelyzero added the source:community Community contribution or request label Mar 9, 2022
Improve Test Coverage automation moved this from Ready! to Done May 2, 2022
@unlikelyzero
Copy link
Collaborator

Demonstrated in Testathon 05/02

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:e2e Needs an e2e test source:community Community contribution or request type:enhancement
Projects
Development

No branches or pull requests

2 participants