enso/app/ide-desktop/lib/dashboard/e2e/signUpWithoutOrganizationId.spec.ts

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
1.1 KiB
TypeScript
Raw Normal View History

/** @file Test the login flow. */
import * as test from '@playwright/test'
import * as actions from './actions'
// =============
// === Tests ===
// =============
test.test('sign up without organization id', async ({ page }) => {
await page.goto('/')
await page.waitForLoadState('domcontentloaded')
await page.goto('/registration')
More E2E tests; `export default` classes from modules (#8730) This is a prerequisite for adding a CI action for E2E tests. - Fix E2E tests - Remove visual regression testing (VRT) and associated fixtures (screenshots) for now - Switch dashboard almost fully to Vite, from ESBuild, to match GUI2's build tooling. - Add some new E2E tests: - Creating assets - Deleting assets - Creating assets from the samples on the home page - Sort assets - Includes fixes for sorting: - Group sorted assets by type again (regression) (see https://github.com/enso-org/cloud-v2/issues/554) - Make sorting by title, case insensitive. This is because it is more intuitive for non-programmers if all items with uppercase names *aren't* separated from those with lowercase names - especially since the Windows FS is case-insensitive. - Normalization of Unicode letters is *not* currently being done. It can potentially be added later. - Double-clicking *anywhere* on a directory row now expands it. Previously it was only being expanded when double clicking - Add recursive label adding/removal to mirror backend - Note: The current implementation is not exactly the same as the backend's implementation. - Fix https://github.com/enso-org/cloud-v2/issues/872 - Unset "saved project details" (for opening the last open project) if fetching it produces an error. # Important Notes - All tests pass. (run `npm run test:e2e` in `app/ide-desktop/lib/dashboard`) - All `npm` commands should be run in `app/ide-desktop/lib/dashboard`. `dashboard:*` npm scripts have been removed from `app/ide-desktop` to prevent a mess. - `npm run dev` confirmed to still work. Note that it has not been changed as it was already using Vite. - `npm run build` now uses `vite build`. This has been tested using a local HTTP server that supports `404.html`. - Other cases have been tested: - `npm run test:e2e` works (all tests pass) - `./run ide build` works - `./run ide watch` works - `./run ide2 build` works - `./run gui watch` works
2024-01-31 14:35:41 +03:00
const api = await actions.mockApi({ page })
api.setCurrentUser(null)
// Sign up
await actions.locateEmailInput(page).fill(actions.VALID_EMAIL)
await actions.locatePasswordInput(page).fill(actions.VALID_PASSWORD)
await actions.locateConfirmPasswordInput(page).fill(actions.VALID_PASSWORD)
await actions.locateRegisterButton(page).click()
// Log in
await actions.locateEmailInput(page).fill(actions.VALID_EMAIL)
await actions.locatePasswordInput(page).fill(actions.VALID_PASSWORD)
await actions.locateLoginButton(page).click()
// Set username
await actions.locateUsernameInput(page).fill('arbitrary username')
await actions.locateSetUsernameButton(page).click()
test
impr(enso/cloud-v2#912): Add `organization_id` and `user_id` fields to `SimpleUser` (#9508) - Updates the model types for the request/response bodies to match the backend. - Renames `CreatePermissionRequestBody::userSubjects` to match `CreatePermissionRequestBody::actorsIds` on the backend - Renames `UserInfo::organization_id` to camel case - Adds `UserInfo::userId` field to match the backend - Merges `SimpleUser` into `UserInfo` Previously, `UserInfo`'s `OrganizationId` was serialized as `pk`. This is not desired since `pk` is an implementation detail (relating to DynamoDB). This commit renames the field to accurately reflect the type of data it contains. - Renames `User::id` to `User::organizationId`. Previously, the user's organization ID was under the `id` field. As of enso-cloud/cloud-v2#1098, this is no longer the case. The `organizationId` field is no longer a user's primary identifier -- `userId` should be used for that purpose instead. So this field has been renamed to `organizationId` to more clearly describe the purpose of the field. Affects the responses expected from the following endpoints: - `PUT /users/me/picture` - `PUT /users/me` - `GET /users/me` - `PUT /users/{userId}/usergroups` - Adds `User::userId` field. Previously, the user's organization ID was used to uniquely identify a user. Now that multiple users can be invited to an organization, it is no longer appropriate to use organization ID to uniquely refer to a user. For this purpose, the backend has introduced the `userId` field. Affects the responses expected from the following endpoints: - `POST /users` - `PUT /users/me/picture` - `PUT /users/me` - `GET /users/me` - `PUT /users/{userId}/usergroups` Removes the `user` param from `tryGetSingletonOwnerPermission`. This param was previously required. It was required because a `userSubject` was necessary to optimistically generate a `UserPermission`. With recent refactors, a `userId` can be used in place of `userSubject` to generate a `UserPermission`. The existing param `owner` provides the `userId`, so the `user` param is redundant and can be removed. - Removes `UserInfo` from the `FullUserSession`. Previously, `UserInfo` in the `FullUserSession` was required to obtain a `userSubject`. Now, `userSubject` has been deprecated in favour of `userId`. `User` provides `userId`, and is present in the `FullUserSession`. Thus, this commit removes `UserInfo` from the `FullUserSession` since it is redundant. - Renames `UserInfo` fields to `camelCase` Previously, `UserInfo`'s fields were serialized as `snake_case`. This is not desired since the convention for the frontend is to use `camelCase` for field names where possible. This commit renames the fields to be `camelCase`, now that the backend has been updated accordingly. - Sorts by `userId` rather than `email` - Compares by `userId` rather than `email` - Extends `User` from `UserInfo` After refactoring, `UserInfo` is now a subset of `User`. To remove duplication, this commit modifies `User` to extend `UserInfo`.
2024-03-27 17:58:08 +03:00
.expect(api.currentUser?.organizationId, 'new user has correct organization id')
.toBe(api.defaultOrganizationId)
})