ericdrosas87
commented
1 month ago Testing notes:
Scenario 1: Successful log in and project selection
- Ensure you have the latest package version installed
- Run the login cell as per usual
- Observe the output of the slug names
- Copy and paste the slug name into the prompt
- Observe the output about the current project being set
- (optional) If the next data curation cell cannot be run, put the mouse cursor focus back on the login cell and then to the data curation cell
- Proceed as usual
Scenario 2: Successful log in, but no project selection
- Ensure you have the latest package version installed
- Run the login cell as per usual
- Observe the output of the slug names
- Either type a non-existent slug name or hit enter into the prompt
- Observe the message that the provided slug name is invalid
- Proceed through the notebook to see the guard rails logging (example: the
cit_sci_pipeline.write_manifest_file()cell)
Scenario 3: Unsuccessful login
- Ensure you have the latest package version installed
- Press enter through the login prompts, not providing a username or password
- Observe how there are no slug names logged
In addition to making the notebooks compatible with the slug listing feature from the PyPI package and the guard rails logging, I also moved several print() statements to the PyPI package so as to clean up the notebook.
Notebooks now compatible with slug selection and guard rails logging