[ https://issues.apache.org/jira/browse/IGNITE-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416768#comment-16416768 ]
Ilya Borisov commented on IGNITE-8028: -------------------------------------- [~alexdel] yesterday I tried to unit test the reset password scenario for {{page-sign-in}} component and, while technically possible, I did not like how complex the task turned out: the page uses several dependencies, which you'd have to manually look for each one and import it into the mock AngularJS module. I think we should consider the following options: 1. Implement a minimal viable SMTP server run by envtools.js. It might also provide a basic way to read received emails. This will allow to run existing e2e/acceptance test in both development and CI environments. 2. Cover {{page-sign-in}} controller with basic unit tests OR move all the business logic into ngrx-style store/effects/service which should be easier to test and simplify the {{page-sign-in}} as much as possible. > Implement unit test for reseting password. > ------------------------------------------ > > Key: IGNITE-8028 > URL: https://issues.apache.org/jira/browse/IGNITE-8028 > Project: Ignite > Issue Type: Test > Components: wizards > Reporter: Alexander Kalinin > Assignee: Alexander Kalinin > Priority: Minor > > We need to cover the case of reseting password in Web Console. For this we > should mock backend mailing services. > Question to think over: > 1) Whether we should mock it on backend or frontend > 2) Should we process a reseting link from response. -- This message was sent by Atlassian JIRA (v7.6.3#76005)