-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Include realistic test scenarios #74
Comments
algattik
changed the title
Include realistic test and integration scenarios
Include realistic test scenarios
Sep 27, 2019
algattik
added a commit
to algattik/MLOpsPython
that referenced
this issue
Nov 28, 2019
* Use Azure CLI tasks to remove need for variables SP_APP_ID, SP_APP_SECRET, SUBSCRIPTION_ID, TENANT_ID * Updated gettin_started.md to point out variable path to artifact (microsoft#117) * Made random hyperparameter (ridge regression alpha) a pipeline parameter, setting its value in the DevOps pipeline (microsoft#107) * Changed unit test to test actual training code (partially solves microsoft#74) * Fixed: attach_compute should set exit code after exception (microsoft#113) * Fixed scoring endpoint HTTP behavior (microsoft#110) * Fixed PipelineParameters format in call to Azure ML Extension (microsoft#118) * Fixed Model build environment for Azure Web App for containers (microsoft#119)
Agree, data connection related tests belong in #75. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The template should include realistic test scenarios, in order to illustrate a proper test strategy and help deal with technical aspects (e.g. folder organization for pytest).
The text was updated successfully, but these errors were encountered: