-
Notifications
You must be signed in to change notification settings - Fork 1.1k
E2E Integration Tests
- Users should be able to create and sign in with their email or username
- Admin should be able to log in and create a new user with a one-time password. A newly created user should be able to log in with that one-time password
- Disabling the sign-up option in the server should disable any signup option from the UI and the API.
- Sign-in with an incorrect user or password should throw "Incorrect username or password".
- User account creation page
- user should be able to select a team
- Test if only joinable teams are listed
- Test if the soft-deleted teams are not listed.
- If the team hierarchy is A -> B -> C. and the B team is soft-deleted, we should move the C team to be under A and allow users to join A -> C.
- Create a new team and make it joinable and test if that appears in the sign-up process
- Create a new team and make it a non-joinable test if that doesn't appear in the sign-up process
- Landing page should load with Zero errors as a non-admin user
- It should have all the assets and their counts correctly on the left side top panel
- Recent views should be either be empty if this the new user who logs in, and it should be relevant recent views if the existing user logs in 3.1 Login as a new user, test if the recent views are empty 3.2 Go to Explore page and look at a new asset (table, pipeline, dashboard, topic, mlmodel) 3.3 All of these should be available in "Recent Views" and should be clickable and go to the respective entity page 3.4 Log out and Log-in, and we should still see the last "Recent Views."
-
Assign ownership of an entity to a logged-in user; it should appear on the landing page
-
Assign ownership to an entity to a team that the logged-in user belongs to; it should appear on the landing page
-
Assign ownership to the logged-in user for about 20 assets. We should only show 5 in and show "View All" the correct count Example:
-
Remove ownership, and it should accurately represent the count in My Data
-
Clicking on any of these entities should take you to the entity page
-
Clicking on the View More should take you to the User Profile -> My Data page
-
Test if the assets indeed belong to the user and/or their teams
-
Test if the pagination works on the My Data page in User Profile
- Follow an entity and make sure that entity appears on the Landing page under the Following section (right-side)
- Follow 20 entities, and we should only show 5 in the Follow Section and show "view all" with the correct count
-
Unfollow an entity, and it should accurately represent the count on the landing page "View All"
-
Clicking on any of these entities should take you to the entity page
-
Clicking on the View More should take you to the User Profile -> "Following" page
-
Test if the assets are indeed followed by the user and/or their teams
-
Test if the pagination works on the Follow page in the User Profile
- The user Should not be able to delete the ingestion bot
- The user Should be able to create a bot with OpenMetadata JWT
AuthMechanism
with token expiry. - Created bot should match the expiry time and
AuthMechanism
- Created bot should match the display name and description on the bot listing as well as on the bot details page
- The user should be able to revoke the token if already present
- The user should be able to Edit the Token expiry and verify the same
- The user should be able to set all these expiration
- 1 Hour
- 1 Day
- 7 Days
- 30 Days
- 60 Days
- 90 Days
- Unlimited Days
- The user should be able to delete the created bot
- MyData Page should render properly with all the required components
- Recent view section and redirection should work for the table entity
- Recent view section and redirection should work for the topic entity
- Recent view section and redirection should work for the dashboard entity
- Recent view section and redirection should work for the pipeline entity
- Listing Recent search terms with redirection should work properly
- My data, following & feed section should work properly for the table entity
- My data, following & feed section should work properly for the topic entity
- My data, following & feed section should work properly for the dashboard entity
- My data, following & feed section should work properly for the pipeline entity
- My data and the following section, CTA should work properly (Skipped)
- Signup and Login with signed-up credentials
- Sign in using invalid credentials
- Forgot password and login with a new password
- Add update and delete Integer custom properties
- Edit created a property for all entities
- Delete created property for all entities
- Add update and delete String custom properties
- Add update and delete Markdown custom properties
- Ingest MySQL data
- Ingest profiler data
- Check if the profiler is ingested properly
- Add table test case with new test suite
- Edit Test Case
- Delete Test Case
- Add Column test case
- Edit column Test Case
- Delete column Test Case
- Delete the Test suite
- Delete MySQL service
- Profiler matrix and test case graph should be visible
- SQL query should be visible while editing the test case
- Add Owner and Tier for entity
- Remove Owner and Tier for entity
- Add and check the active announcements for the entity
- Delete entity flow should work properly
- Edit lineage for all entities
- Add announcement and verify the active announcement for the entity
- Create a new glossary
- Verify added glossary details
- Create glossary term
- Updating data of glossary
- Updating data of glossary term
- Check the Assets Tab (add glossary term to the entity)
- Remove the Glossary term from the entity
- Delete glossary term
- Delete glossary
- Default Policies and Roles should be displayed
- Add new policy
- Edit policy description
- Add a new rule
- Edit rule name for created Rule
- Delete new rule
- Delete the last rule and validate
- Delete created policy
- Default Roles and Policies should be displayed
- Add a new role and check all tab data
- Add a new role without selecting data
- Edit created role
- Add a new policy to the created role
- Remove added policy from the created role
- Check if the last policy is not removed
- Delete created Role
- Create and Assign a role to a user
- Add the service
- Update service description and owner
- Required Details should be available
- Add new tag category flow
- Add new tag flow
- Use a newly created tag for any entity
- Check the Usage of the tag and it should redirect to explore page with the tags filter
- Delete Tag flow