Jans VM Pre Release Test Plan

For the following operating systems

• SUSE Leap 15
• RHEL 8
• Ubuntu 20
• Ubuntu 22
• Ubuntu 24

For the following database:

• MySQL
• Postgres

This implies we need to do 14 test installations...

• Install software according to the docs, including running setup
• Review .well-known config files: openid, fido, uma, scim, lock-server
• Start the TUI and use device-flow for login
• Jans Tent: test login using password authentication, acr=simple_password_auth
• Jans Tent: test Agama Project deployment, acr=agama_org.gluu.agama.smtp.main

The QA team needs to follow writing in a journal the day to day activities and commands run. With several iterations this should help us automate as much as possible to make their job easier.

Proposed agenda for Pre-release review meeting:

• A build is marked as a Release candidate couple of days in advance via polls i.e. https://github.com/JanssenProject/jans/discussions/4280
• Testers need to test release candidate build against sanity tests and give status during the meeting
• Check that all changes that are part of this release have updated corresponding documentation, and provide status during this meeting
• Support function should be aware/briefed on upcoming changes as part of the release
• Release notes for majore.minor changes only (not changelog) should be prepared in advance to give the user a head up on what changed in summary and reviewed in this meeting.Release notes should accompany release announcements on social media and community forums.