Adding local Cypress files and demo functional test

[AvivBenchorin]

Description

With the existing repository, there is not yet functionality to run Cypress or other test writing software. This PR aim to further sets up the repository for proper development by adding TypeScript and ESLint as dependencies, and creating the Cypress folder structure. It also adds a demo Cypress functional test to be run on OpenSearch Dashboards, as well as updates the .gitignore and the index.js file under the support Cypress directory.

Signed-off-by: Aviv Benchorin [email protected]

Issues Resolved

N/A

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

[tianleh]

1. Make sure the commits are squashed into one commit when merging.

2. Add Eslint for easy formatting. https://eslint.org/docs/user-guide/getting-started (OK to do it in a follow up PR)

[riysaxen-amzn]

Follow Javascript standards to document the code refer https://gomakethings.com/whats-the-best-way-to-document-javascript/ for best practices.

[kavilla]

Looks cool so far, would be possible to add a quick note in the README on how to run the tests. Save some time for others. For me I ran through https://docs.cypress.io/guides/getting-started/installing-cypress#System-requirements and I seem to be able to get the test running but it hangs.

[kavilla]

1. Make sure the commits are squashed into one commit when merging.

2. Add Eslint for easy formatting. https://eslint.org/docs/user-guide/getting-started (OK to do it in a follow up PR)

+1 to both,

1. Technically all commits are reviewable, and I see some merge commits. I recommend rebasing for those so an extra commit doesn't show up. Makes the commit history more clean and cool. 😎

[ananzh]

Aviv, maybe you can create an issue to document any thoughts, designs, discussions and any progresses. Later, you can decide to close it or leave it for other people to contribute. An example here for reference.

Meanwhile for this PR, probably better to give a bit more intro in the Description. I would suggest to formalize your PR and give more details. Here are two examples:
#392
#540

I think you can write the discussion or thoughts in either issue/PR. If you have multiple PRs then I would suggest write more details in issue.

[AvivBenchorin]

Looks cool so far, would be possible to add a quick note in the README on how to run the tests. Save some time for others. For me I ran through https://docs.cypress.io/guides/getting-started/installing-cypress#System-requirements and I seem to be able to get the test running but it hangs.

Added more details to README.

[seraphjiang]

add how to run eslint into readme. Not necessary in this PR, you might address this in future PR.

[AvivBenchorin]

Will address in next PR.