tests for create user flow

[christopherjturner]

[feedmypixel]

A couple of things:

1. For interacting with forms there is the form component https://github.com/DEFRA/cdp-portal-tests/blob/main/test/components/form.component.js

This selects form controls by their label text, or button text, so you don't have to make custom nextButton or searchByAADName methods. This is also implicitly testing that the forms and form controls are built correctly.

fEx:

      await FormComponent.inputLabel('Name').click()
      await browser.keys(testRepositoryName)

      await FormComponent.inputLabel('Template').click()
      await browser.keys(serviceType)

      await FormComponent.inputLabel('Owning Team').click()
      await browser.keys('Platform')

      await FormComponent.submitButton('Next').click()

2. Have you read this? finding-elements-in-tests. It explains why using css selectors or ids is brittle and prone to breaking. And how to write test hooks so that when a dev is working in the Portal Frontend they can easily see that the element is being references in tests.