Skip to content

Conversation

@ibrahimmunir14
Copy link
Contributor

Welcome Email page
localhost_44363_TrackingSystem_Delegates_Register_WelcomeEmail
localhost_44363_TrackingSystem_Delegates_Register_WelcomeEmail (1)

Password page
localhost_44363_TrackingSystem_Delegates_Register_Password

Summary page (if welcome email set)
localhost_44363_TrackingSystem_Delegates_Register_Summary

Summary page (if welcome email not set)
localhost_44363_TrackingSystem_Delegates_Register_Summary (1)

Copy link
Contributor

@AlexJacksonDS AlexJacksonDS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few questions/comments but overall looks good.

Copy link
Contributor

@AlexJacksonDS AlexJacksonDS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one minor thing to change

</label>
</div>

<div class="@emailDateCss @errorCss" id="conditional-welcome-email-date">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be worth putting the form error in the VC, like we do with text-inputs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alex suggested this too, but can't see a way to do it nicely. The error message is in the VC, but the red border styling is not. The reason being that the css for that is affected by the conditional.

private IJobGroupsDataService jobGroupsDataService = null!;
private IUserDataService userDataService = null!;
private IUserService userService = null!;
private ICryptoService cryptoService = null!;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to add any tests about temp data being updated appropriately?

Copy link
Contributor Author

@ibrahimmunir14 ibrahimmunir14 Jul 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've already written tests for populating DelegtateRegistrationbyCentreData from viewmodels. Is that enough?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if someone refactors this file and forgets to update TempData? I guess we could catch that in the AutomatedUI tests, when we do accessibility scans of the pages (which I'm happy for you to add as part of whichever subtask)

@ibrahimmunir14 ibrahimmunir14 requested a review from stellake July 14, 2021 15:37
Copy link
Contributor

@stellake stellake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - can we rename one of the methods, then merge this without rereview. Let's add accessibility tests as part of your second review. 🙏

@ibrahimmunir14 ibrahimmunir14 merged commit ff88697 into master Jul 15, 2021
@stellake stellake deleted the HEEDLS-546-all-delegates-register-3-4-5 branch July 15, 2021 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants