Enhance e2e (end-to-end) tests for MyDSpace page (Part 2)

[oscar-escire]

References

• Fixes Enhance e2e (end-to-end) tests for MyDSpace page #3985 (Second part)

Description

This PR includes three new tests for the My-DSpace page. Specifically, the three new tests are:

• Start a new Submission of various types using the "+" dropdown
• Start a new Submission of various types using the "import" dropdown
• Test the "see", "return to pool", "edit", "reject" and "approve" workflow items buttons
• Test actions in supervised item view

Instructions for Reviewers

1. Start DSpace in dev mode
2. Open Cypress with (cypress:run)
3. Run the my-dspace.ts tests and you will see the three new tests in the list.

List of changes in this PR:

• Added describe section for testing supervised items to my-dspace.cy.ts file
• Added describe section for testing workflow tasks to my-dspace.cy.ts file
• Added describe section for testing import external items to my-dspace.cy.ts file
• Added describe section for testing new submissions button to my-dspace.cy.ts file

Checklist

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.