Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-519

As a QE, I want to test the minimal python notebook image to ensure it behaves as expected

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • None
    • False
    • False
    • Hide

      1) JupyterHub instance can be spawned using this image
      2) The available libraries pre-installed match the requirements
      3) The User is able to use Pip in the way specified by the requirements
      4) Code runs correctly/accurately in the notebook(s) (smoke tests e.g. hello world or simple function, library imports, light ML loads via libraries e.g. linear regression, random forests)

      Show
      1) JupyterHub instance can be spawned using this image 2) The available libraries pre-installed match the requirements 3) The User is able to use Pip in the way specified by the requirements 4) Code runs correctly/accurately in the notebook(s) (smoke tests e.g. hello world or simple function, library imports, light ML loads via libraries e.g. linear regression, random forests)
    • No
    • No
    • Undefined
    • No
    • Pending
    • None
    • RHOSi 0.1, RHOSi 0.2

      The minimal python notebook image should be tested to ensure that:

      1) It is available and selectable from the spawner UI
      2) The User is able to spawn a JupyterHub instance based on this image
      3) This image comes preinstalled with Python v.3.6.8  v.3.8 and nothing else*
      4) Python code runs correctly in the notebook(s)
      5) The User is able to install/upgrade additional libraries via Pip**
      6) Additional libraries installed by the User are usable in the notebook and work as expected

      *: Some additional libraries will inevitably be present (e.g. Jupyter and its dependencies). There is a need to document which libraries are expected in this image we can assume that jupyter and all its dependencies will be there and nothing else.
      **: The behaviour of pip is still not clearly defined and needs to be documented. Additional testing might be needed depending on the captured requirements
      The user should be able to use pip however they want.

              rhn-support-lgiorgi Luca Giorgi
              rhn-support-lgiorgi Luca Giorgi
              Luca Giorgi Luca Giorgi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: