Release 0.3

Summary

#54 (closed)

Focus

Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there spezifications? Are they satisfied?

For further good practices have a look at our review guidelines.

README_SETUP.md

@@ -8,14 +8,16 @@ git clone 'https://gitlab.com/caosdb/caosdb-advanced-user-tools'
 ```
 
 ## Dependencies
-Dependencies will be installed automatically if you use the below described procedure.
-- `caosdb>=0.4.0`                                      
+Dependencies will be installed automatically if you use the below described
+procedure.
+- `caosdb>=0.6.0`
 - `openpyxl>=3.0.0`
 - `xlrd>=1.2.0`
--  `pandas>=1.2.0`
+- `pandas>=1.2.0`
 - `numpy>=1.17.3`
 
-If you want to use the optional h5-crawler the following dependencies will be installed additionally:
+If you want to use the optional h5-crawler the following dependencies will be
+installed additionally:
 - `h5py>=3.3.0`
 
 For testing:
@@ -35,16 +37,15 @@ Optional h5-crawler:
 ## Run Integration Tests Locally
 
 1. Change directory to `integrationtests/`.
-2. Mount `extroot` to the folder that will be used as
-   extroot. E.g. `sudo mount -o bind extroot
-   ../../caosdb-deploy/profiles/empty/paths/extroot` (or whatever path
-   the extroot of the empty profile to be used is located at).
-3. Start (or restart) an empty (!) CaosDB instance (with the mounted extroot).
-   The database will be cleared during testing, so it's important to use
-   an empty instance.
-   Make sure your configuration for the python caosdb module is correct and
-   allows to connect to the server.
-4. Run `test.sh`.  Note that this may modify content of the `integrationtest/extroot/` directory.
+2. Mount `extroot` to the folder that will be used as extroot. E.g. `sudo mount
+   -o bind extroot ../../caosdb-deploy/profiles/empty/paths/extroot` (or
+   whatever path the extroot of the empty profile to be used is located at).
+3. Start (or restart) an empty (!) CaosDB instance (with the mounted
+   extroot). The database will be cleared during testing, so it's important to
+   use an empty instance. Make sure your configuration for the python caosdb
+   module is correct and allows to connect to the server.
+4. Run `test.sh`. Note that this may modify content of the
+   `integrationtest/extroot/` directory.
 
 ## Code Formatting
 `autopep8 -i -r ./`