status-desktop/test/e2e/gui/components/change_password_popup.py

import allure

import driver
from constants.settings import PasswordView
from gui.components.base_popup import BasePopup
from gui.elements.button import Button
from gui.elements.text_label import TextLabel
from gui.objects_map import names


class ChangePasswordPopup(BasePopup):

    def __init__(self):
        super(ChangePasswordPopup, self).__init__()
        self.re_encrypt_data_restart_button = Button(names.reEncryptRestartButton)
        self.re_encryption_complete_element = TextLabel(names.reEncryptionComplete)

    def click_re_encrypt_data_restart_button(self):
        """
        Timeout is set as rough estimation of 30 seconds. What is happening when changing password is
        the process of re-hashing DB initiated. Taking into account the user is new , so DB is relatively small
        I assume, 30 seconds should be enough to finish re-hashing and show the Restart button
        This time is not really predictable, especially for huge DBs.
        In case it does not please check https://github.com/status-im/status-desktop/issues/13013 for context
        """
        self.re_encrypt_data_restart_button.click()
        assert driver.waitForObject(self.re_encryption_complete_element.real_name, 30000), \
            f'Re-encryption confirmation is not present within 30 seconds'
        assert driver.waitForObject(self.re_encrypt_data_restart_button.real_name, 30000)
        assert getattr(self.re_encrypt_data_restart_button.object, 'text') == PasswordView.RESTART_STATUS.value
        self.re_encrypt_data_restart_button.click()