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

Initial implementation of the application performance testing capabilities #28

Open
bevalentin opened this issue Jan 21, 2025 · 0 comments
Assignees

Comments

@bevalentin
Copy link
Collaborator

Initial implementation of the application performance testing capabilities

  • Different types of "applications" require different solutions: EO Application Packages, Jupyter notebooks, OpenEO workflows
  • Application artifacts identified by parameter or discovered dynamically (automatic search for .ipynb files).
  • Requires providing test inputs or test scripts in application repositories. These scripts may perform different types of tests: unit, performance, validation, etc. and must output the results in a structured format.
  • Applications built (as necessary), deployed and executed with test inputs or using the scripts
  • Execution outputs and resource usage information are collected and available in reports
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants