Run mvesuvio before uploading package

During the nightly deployment workflow, it's best to test
the basic functunality of config and make sure that
at least this command does not give an error.

In the case of conda, this is best done in the conda recipe,
by adding a test section that runs the command for config.
(Also added command to run unit tests)

.github/actions/publish-pypi-package/action.yml

@@ -14,13 +14,26 @@ runs:
     shell: bash -l {0}
     run: |
       conda config --set always_yes yes --set changeps1 no
-      conda create -n build-env-pypi python=3.10.*
-      conda activate build-env-pypi
-      mamba install -c conda-forge python-build twine 
+      conda create -n build-env-pypi -c conda-forge python=3.10.* python-build twine
 
   - name: Build package
     shell: bash -l {0}
     run: |
       conda activate build-env-pypi
       python -m build
+      conda deactivate
+
+  - name: Test basic functunality of mvesuvio
+    shell: bash -l {0}
+    run: |
+      mamba create -n mvesuvio-test
+      conda activate mvesuvio-test 
+      pip install dist/*.whl
+      mvesuvio config
+      conda deactivate 
+
+  - name: Upload to PyPI
+    shell: bash -l {0}
+    run: |
+      conda activate build-env-pypi
       twine upload -u __token__ -p ${{ inputs.token }} dist/*

.github/workflows/deploy_conda_nightly.yml

@@ -24,6 +24,7 @@ jobs:
       - name: Check for changes since last build
         run: |
           echo "recentCommits=$(test -z $(git log --since="yesterday" -1 --format=%h) && echo false || echo true)" >> $GITHUB_ENV
+
       - name: Setup Miniconda
         if: ${{ env.recentCommits == 'true'}}
         uses: conda-incubator/[email protected]

conda/meta.yaml

@@ -34,6 +34,15 @@ requirements:
 test:
   imports:
     - mvesuvio
+  requires:
+    - pytest
+    - mock 
+  source_files:
+    - tests/unit/
+    - tools/
+  commands:
+    - pytest
+    - mvesuvio config    
 
 about:
   home: https://github.com/mantidproject/vesuvio