e2e test setup & test implementation

[koebel]

Description

• setup for e2e tests
• implementing tests scenario steps

IMPORTANT:
Scenario steps relating to assertion if object modifications like zoom and rotation have been applied haven't yet been implemented in this PR and it seems like assertions regarding position of model, etc. might not even be possible. According to this blog Playwright doesn't offer specific support for interaction with WebGL. WebGL is just rendered as canvas element in HTML, with which the user can interact with using the mouse and script it using JavaScript. However it seems like the actual model is not accessible through HTML. Therefore these steps of the scenario have been removed for now and a new issue has been created for this, see #15

Related Issue

• Relates to add E2E test coverage #9

Motivation and Context

add test coverage

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added

[phil-davis]

Thoughts from me. But I am not regularly working on these kind of UI tests, so please let me know any better ideas/conventions/standards.

[saw-jan]

I am happy to merge it as it is now.
Thank you for your effort 👍