Notes for 4.0 QA testers

High level checks

1. installation succeeds
2. The app starts (and you can login with some user)
3. uninstallation works
4. casa and oxd-server services survive after gluu or VM restart.
5. The app works fine after restarts take place

Additionally after installation finishes (previous to login) we need to check:

• /install/community-edition has file casa_cleanup.py with execution permissions
• File /etc/gluu/conf/casa.json has authz_redirect_uri/post_logout_uri/frontchannel_logout_uri fields and they start like "https://hostname..", not localhost!
• File /etc/gluu/conf/casa.json has a client section in it (no section means there was a problem of casa <--> oxd for client registration)
• In oxtrust a new custom script named casa appears enabled in person authentication tab
• In oxtrust a new custom script named casa_client_registration appears enabled in client registration tab
• In oxtrust there is a new OIDC client named gluu-casa_*. Has scopes openid, profile, user_name, clientinfo, uma_protection. Also its expiration is in one year from now
• There are 5 scripts starting with "casa" in /opt/gluu/python/libs

Here is how you can check if uninstallation did the job:

• The 2 custom scripts were removed
• The openid client was removed
• 5 scripts in /opt/gluu/python/libs were removed
• dir /opt/gluu/jetty/casa does not exist
• file /etc/gluu/conf/casa.json does not exist
• service casa does not exist

Side note: Ensure casa also works properly when using couchbase backend. IMO, testing one rpm and one deb-based distro should suffice.