Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebTop 5.26.1 #7033

Closed
5 tasks done
Amygos opened this issue Sep 23, 2024 · 15 comments
Closed
5 tasks done

WebTop 5.26.1 #7033

Amygos opened this issue Sep 23, 2024 · 15 comments
Assignees
Labels
verified All test cases were verified successfully

Comments

@Amygos
Copy link
Member

Amygos commented Sep 23, 2024

Upgrade WebTop to release 5.26.1

Required modifications:

Amygos added a commit to NethServer/webtop5 that referenced this issue Sep 23, 2024
Amygos added a commit to NethServer/nethserver-webtop5 that referenced this issue Sep 23, 2024
@nethbot
Copy link
Member

nethbot commented Sep 23, 2024

in 7.9.2009/testing:

@nethbot
Copy link
Member

nethbot commented Sep 23, 2024

in 7.9.2009/testing:

@Amygos
Copy link
Member Author

Amygos commented Sep 25, 2024

Testing release: ghcr.io/nethserver/webtop:1.0.22-testing.4

@Amygos Amygos added the testing Packages are available from testing repositories label Sep 25, 2024
@Amygos
Copy link
Member Author

Amygos commented Sep 25, 2024

Test Case 1: Verify that a new installation of WebTop testing version works correctly

Description: Ensure that WebTop's testing version functions correctly after a fresh installation of the module.
Pre-conditions:

  • A fresh installation of the WebTop testing module is available.
  • The installation is performed on a compatible system.

Steps:

  1. Install the WebTop testing module.
  2. Follow the standard installation steps for the module.
  3. Open WebTop after installation.
  4. Verify that all basic features (login, main page, settings) function correctly.

Expected Result: WebTop's testing version should work without any errors after installation.
Post-conditions: None.


Test Case 2: Verify that an update to WebTop testing version functions correctly

Description: Ensure that updating WebTop to the testing version from a previous version works without issues.
Pre-conditions:

  • The previous version of WebTop is installed.
  • The update module for the WebTop testing version is available.

Steps:

  1. Perform the update from the previous version to the WebTop testing version.
  2. Open WebTop after the update.
  3. Verify that existing data and settings are retained.
  4. Test core features (login, user data, settings) to ensure functionality.

Expected Result: The update to the WebTop testing version should be successful, and all features should work as expected.
Post-conditions: None.


Test Case 3: Verify that the new login page of WebTop testing version loads correctly

Description: Ensure that the new login page is properly loaded in WebTop testing version.
Pre-conditions: None.

Steps:

  1. Open WebTop.
  2. Navigate to the login page.
  3. Observe the page loading.

Expected Result: The new login page should load without any errors.
Post-conditions: None.


Test Case 4: Verify that the new theme is the default in new installations of WebTop testing version

Description: Ensure that the newly introduced theme is set as the default for fresh installations of the WebTop testing version.
Pre-conditions:

  • A fresh installation of the WebTop testing module is available.

Steps:

  1. Install the WebTop testing module.
  2. Open WebTop after installation.
  3. Verify that the new theme is applied by default.

Expected Result: The new theme should be the default theme in the WebTop testing version.
Post-conditions: None.


Test Case 5: Verify that users are prompted to try the new theme during migration or update to WebTop testing version

Description: Ensure that users are asked to try the new theme when migrating or updating to the WebTop testing version.
Pre-conditions:

  • For Migration: The previous version of the WebTop module must be installed on NethServer 7.
  • For Update: The older version of WebTop is installed, and the new theme should be part of the testing update module.

Steps:

  1. Perform the migration or update to the WebTop testing version.
  2. Open WebTop after the update.
  3. Verify that the user is prompted to choose between keeping the new theme or reverting to the old one.

Expected Result: After the update or migration, the user should be prompted to either keep the new theme or revert to the old one.
Post-conditions: None.


Test Case 6: Verify that the new landing page in WebTop testing version is the Mail service

Description: Ensure that the default landing page after login in the WebTop testing version is the Mail service.
Pre-conditions: None.

Steps:

  1. Open WebTop and log in with valid credentials.
  2. Observe the landing page after login.

Expected Result: The landing page should be the Mail service in the WebTop testing version.
Post-conditions: None.


Test Case 7: Verify that the calendar scheduler in WebTop testing version has a time resolution of 15 minutes

Description: Ensure that the calendar scheduler allows selecting time slots in 15-minute intervals in the WebTop testing version.
Pre-conditions: None.

Steps:

  1. Open WebTop.
  2. Navigate to the calendar scheduler.
  3. Try to schedule a new event.
  4. Verify that time slots are available in 15-minute increments.

Expected Result: The time resolution in the calendar should be 15 minutes in the WebTop testing version.
Post-conditions: None.


Test Case 8: Verify that adding new domains is not possible in WebTop testing version's admin interface

Description: Ensure that the multiple domain mode option is available but that new domains cannot be added via the admin interface in the WebTop testing version.
Pre-conditions: Access to WebTop's admin interface.

Steps:

  1. Log in to the admin interface of WebTop.
  2. Navigate to the multiple domain mode settings.
  3. Right-click to open the context menu for adding a new domain.
  4. Attempt to select the option to add a new domain.

Expected Result: The context menu for adding a new domain should appear, but it should be unclickable or grayed out, preventing the addition of new domains.
Post-conditions: None.


Test Case 9: Check that the LogViewer panel is not present in admin management of WebTop testing version

Description: Ensure that the LogViewer panel is not present in the admin management interface of the WebTop testing version.
Pre-conditions: Access to the admin management interface.

Steps:

  1. Log in to the admin management interface.
  2. Navigate to the relevant section for system panels.
  3. Verify that the LogViewer panel is not present.

Expected Result: The LogViewer panel should not be present in the admin management interface of WebTop testing version.
Post-conditions: None.

@Amygos Amygos mentioned this issue Sep 26, 2024
7 tasks
@lucagasparini
Copy link

lucagasparini commented Sep 26, 2024

Test case 1,2,3,4,6,7,8,9 : VERIFIED

In test case 5 (migration from NS7) these settings are missing:

  • Mail module as default: ('com.sonicle.webtop.core','default.startup.service','com.sonicle.webtop.mail')
  • Calendar with 15-minute resolution: ('com.sonicle.webtop.calendar','default.scheduler.timeresolution','15')
  • PEC Bridge enabled: ('com.sonicle.webtop.core','config.pecbridge.management','true') (if not already present)

@Amygos Amygos removed the testing Packages are available from testing repositories label Sep 26, 2024
@Amygos
Copy link
Member Author

Amygos commented Sep 26, 2024

The test case 5 is only about the new theme and can be marked as verified.
I will add a new test case for the new issues.

@Amygos
Copy link
Member Author

Amygos commented Sep 27, 2024

Testing release: ghcr.io/nethserver/webtop:1.0.22-testing.5

@Amygos Amygos added the testing Packages are available from testing repositories label Sep 27, 2024
@Amygos
Copy link
Member Author

Amygos commented Sep 27, 2024

Execute the new test case and test case 1&2 to check if there is any regression.

@Amygos
Copy link
Member Author

Amygos commented Sep 27, 2024

Test Case 10: Verify new controls after migration to WebTop testing version

Description: Ensure that after migrating to the WebTop testing version, specific settings and modules are correctly applied: the Mail module as the default landing page, the calendar scheduler with a 15-minute time resolution, and the PEC Bridge is enabled.
Pre-conditions:

  • The previous version of the WebTop module is installed on NethServer 7.
  • A migration to the WebTop testing version is performed.

Steps:

  1. Migrate from the previous version of WebTop to the WebTop testing version.
  2. Open WebTop after migration.
  3. Verify that the Mail module is the default landing page upon login.
  4. Navigate to the calendar scheduler and verify that the time resolution is set to 15 minutes.
  5. Access the PEC Bridge settings and verify that the PEC Bridge is enabled.

Expected Result:

  • The Mail module is set as the default landing page after login.
  • The calendar scheduler allows selecting time slots in 15-minute intervals.
  • The PEC Bridge is enabled and operational.
    Post-conditions: None.

@lucagasparini
Copy link

Repeated test cases 1&2 with webtop:1.0.22-testing.5 > VERIFIED
Test case 10 > VERIFIED

@lucagasparini lucagasparini added the one week quarantine 😷 Packages must remain almost one week in the testing repository before the release label Sep 27, 2024
@Amygos Amygos added verified All test cases were verified successfully and removed verified All test cases were verified successfully testing Packages are available from testing repositories labels Sep 27, 2024
Amygos added a commit to NethServer/webtop5 that referenced this issue Sep 30, 2024
@Amygos Amygos changed the title WebTop 5.26.0 WebTop 5.26.1 Sep 30, 2024
@nethbot
Copy link
Member

nethbot commented Sep 30, 2024

in 7.9.2009/testing:

@Amygos
Copy link
Member Author

Amygos commented Sep 30, 2024

Testing release: 1.0.22-testing.7

@Amygos
Copy link
Member Author

Amygos commented Sep 30, 2024

Test Case 11: Verify that the "What's New" window does not open after login on new installations, updates, or migrations

Description: Ensure that the "What's New" window does not appear after logging in to WebTop testing version on new installations, updates, or migrations.
Pre-conditions:

  • WebTop testing version has been installed, updated, or migrated.

Steps:

  1. Open WebTop and log in with valid credentials.
  2. Observe whether the "What's New" window appears after login.

Expected Result: The "What's New" window should not appear after login in new installations, updates, or migrations.
Post-conditions: None.

@Amygos Amygos added the testing Packages are available from testing repositories label Sep 30, 2024
@lucagasparini
Copy link

Test case 10 successfully passed for new installation, upgrade and migration from NS7 👍

@lucagasparini lucagasparini added verified All test cases were verified successfully and removed testing Packages are available from testing repositories labels Sep 30, 2024
@DavidePrincipi DavidePrincipi moved this from New to In progress in NethServer Oct 7, 2024
@lucagasparini lucagasparini removed the one week quarantine 😷 Packages must remain almost one week in the testing repository before the release label Oct 11, 2024
@DavidePrincipi
Copy link
Member

Released in

@github-project-automation github-project-automation bot moved this from In progress to Done in NethServer Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verified All test cases were verified successfully
Projects
Status: Done
Development

No branches or pull requests

4 participants