-
Notifications
You must be signed in to change notification settings - Fork 2
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
epic: Automated Testing for Built-in Models #56
Labels
type: feature request
A new feature
Comments
Van-QA
changed the title
feat: Automate e2e testing for common models in Hugging Face Cortexso Hub
test: Automate e2e testing for common models in Hugging Face Cortexso Hub
Sep 6, 2024
dan-homebrew
changed the title
test: Automate e2e testing for common models in Hugging Face Cortexso Hub
test: Automate e2e testing for cortex.cpp install and inference request on major platforms
Sep 6, 2024
dan-homebrew
changed the title
test: Automate e2e testing for cortex.cpp install and inference request on major platforms
test: Automated e2e testing for cortex.cpp install and inference request on major platforms
Sep 6, 2024
dan-homebrew
changed the title
test: Automated e2e testing for cortex.cpp install and inference request on major platforms
test: Automated Testing for Built-in Models
Sep 8, 2024
0xSage
changed the title
test: Automated Testing for Built-in Models
epic: Automated Testing for Built-in Models
Sep 23, 2024
List current models and quantization
|
I will write test for default |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Resources
Original Post
Problem
To avoid manually test the end-to-end functionality of various models in the Hugging Face Cortex Hub. This process is time-consuming and prone to human error, leading to inconsistencies in testing results.
Success Criteria
I want to have an automated end-to-end testing framework set up for the most common models in the Hugging Face Cortex Hub. This framework should automatically run tests for the following models:
The tests should be executed either
The results should be easily accessible and provide clear feedback on the models' performance and functionality.
Additional Context
Automating the testing process will not only save time but also ensure that any changes or updates to the models do not break existing functionality. It would be beneficial to integrate this testing with CI/CD pipelines to ensure that any new model versions are automatically tested before deployment.
The text was updated successfully, but these errors were encountered: