I'm interested in defining a minimum set of high-level operations which should be validated over a page using the Page Object Model in Selenium Automation Framework.

So far I know about the following:

1. Navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. Fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. Submit - Submit the form. Implemented as submitCustomerCreationPage().
4. Cancel - Cancel the form submission.
5. Back - Navigate back from page.
6. Click - Click any field on page.
7. Verify - Verify any field related attributes/values on page.
8. Upload/download - Perform upload/download of a file on page.
9. Expand/collapse - Expand/collapse any sections on page.
10. Close - Close the page.

Are there any other high-level operations that should be added to the above list?

I'm interested in defining a minimum set of high-level operations which should be validated over a page using the Page Object Model in Selenium Automation Framework.

So far I know about the following:

1. Navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. Fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. Submit - Submit the form. Implemented as submitCustomerCreationPage().
4. Cancel - Cancel the form submission.
5. Back - Navigate back from page.
6. Click - Click any field on page.
7. Verify - Verify any field related attributes/values on page.
8. Upload/download - Perform upload/download of a file on page.
9. Expand/collapse - Expand/collapse any sections on page.
10. Close - Close the page.

Are there any other high-level operations that should be added to the above list?

Update: I'm looking for atomic page-level operations and not business/functionality level operations. Create, Edit, View, Delete, Search, etc. are business/functional level operations. For example, creation involves navigation to the page (Navigate), filling the form (Fill) and click on Save (Submit). As you can see creation is not atomic in nature to the page, it is a function of the application and not the page. I hope this explanation improves the clarity of the question. Thanks.

I'm interested in defining a minimum set of high-level minimum operations which should be validated over a page using the Page Object Model in Selenium Automation Framework.

So far I know about the following:

1. Navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. Fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. Submit - Submit the form. Implemented as submitCustomerCreationPage().
4. Cancel - Cancel the form submission.
5. Back - Navigate back from page.
6. Click - Click any field on page.
7. Verify - Verify any field related attributes/values on page.
8. Upload/download - Perform upload/download of a file on page.
9. Expand/collapse - Expand/collapse any sections on page.
10. Close - Close the page.

Are there any other high-level operations that should be added to the above list?

I'm interested in defining a minimum set of high-level operations which should be validated over a page using the Page Object Model in Selenium Automation Framework.

So far I know about the following:

1. Navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. Fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. Submit - Submit the form. Implemented as submitCustomerCreationPage().
4. Cancel - Cancel the form submission.
5. Back - Navigate back from page.
6. Click - Click any field on page.
7. Verify - Verify any field related attributes/values on page.
8. Upload/download - Perform upload/download of a file on page.
9. Expand/collapse - Expand/collapse any sections on page.
10. Close - Close the page.

Are there any other high-level operations that should be added to the above list?

I'm interested in defining a set of high-level minimum standard operations which should be implemented when automation using the Page Object Model in Selenium Automation Framework.

So far I know of the following:

1. navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. submit - Submit the form. Implemented as submitCustomerCreationPage().
4. cancel - Cancel the form submission.
5. back - Navigate back from page.
6. click - Click any field on page.
7. verify - Verify any field related attributes/values on page.
8. upload/download - Perform upload/download of a file on page.
9. expand/collapse - Expand/collapse any sections on page.
10. close - Close the page.

Are there any other high-level operations that can be added to the above list?

I'm interested in defining a minimum set of high-level minimum operations which should be validated over a page using the Page Object Model in Selenium Automation Framework.

So far I know about the following:

1. Navigate - Used to navigate to the page. Implemented as navigateToHomepage()
2. Fill - Used to fill any forms or sections of form on the page. Implemented as fillLoginPage(), fillEmployeeAddressSection(), etc.
3. Submit - Submit the form. Implemented as submitCustomerCreationPage().
4. Cancel - Cancel the form submission.
5. Back - Navigate back from page.
6. Click - Click any field on page.
7. Verify - Verify any field related attributes/values on page.
8. Upload/download - Perform upload/download of a file on page.
9. Expand/collapse - Expand/collapse any sections on page.
10. Close - Close the page.

Are there any other high-level operations that should be added to the above list?