This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

Test procedure before a release

Jump to bottom

Hans Permana edited this page Jun 6, 2018 · 16 revisions

The purpose of this document is to standardize the testing procedure after each build so that some steps are note missed.

Steps

remove all pre-existing files from the previous installations:
- ~/.cate
- ~/cate-x.x.x
- <miniconda_dir>/envs/cate-env
- ~/.local/? (something that indicates a python library)
make sure there are no running webapi servers in the machine (also under different users). It can also be verified by opening http://localhost:9090. It should not be accessible.
install cate-desktop-setup-2.x.x using the binary
Run Cate Desktop

Test 06.06.2018

MacOS

fresh install cate-2.0.0-dev.12
- installation finished successfully, Cate Desktop started normally

Ubuntu 16.04 LTS

fresh install cate-2.0.0-dev.12
- installation finished successfully, Cate Desktop started normally
- [question] when saving workspace with specified directories, is it normal that nothing is stored in this directory? The tool is still able to restore the previous state, though.

Windows 10 Home

fresh install cate-2.0.0-dev.12
- installation finished successfully, Cate Desktop started normally