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

Determine best structure for integration tests across extensions #406

Closed
Tracked by #412
timkimadobe opened this issue Sep 27, 2023 · 0 comments
Closed
Tracked by #412
Assignees
Labels
task Item that can be completed as a standalone code change or is part of an epic.Used by issue templates

Comments

@timkimadobe
Copy link
Contributor

Task description

The two main options are:

  1. A shared repo that owns all integration tests for extensions, with the test utilities also residing there
  2. Integration tests are owned by each respective extension, and they import the test utilities they need

Approaches for each case, in the given scenarios

Running for all extensions

  1. Run the integration test repo job
  2. Need to have the caller call each repo's integration test job (and handle orchestration, be able to listen for pass/fail, etc)

Running for specific extension

  1. Given tests are grouped by extension, run only tests related to specific extension
  2. Run the repo's integration test job

Local development

  1. Pull the integration tests into local project and run. If changes to integration tests are required, need to go to a separate repo to make updates
  2. Run the integration test suite (as it is already part of the project)

Additional implementation details or code snippet(s)

No response

@timkimadobe timkimadobe added the task Item that can be completed as a standalone code change or is part of an epic.Used by issue templates label Sep 27, 2023
@timkimadobe timkimadobe self-assigned this Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task Item that can be completed as a standalone code change or is part of an epic.Used by issue templates
Projects
None yet
Development

No branches or pull requests

2 participants