Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add e2e test to simulate resize behavior in calcite-text-area #6624

Open
anveshmekala opened this issue Mar 21, 2023 · 0 comments
Open

add e2e test to simulate resize behavior in calcite-text-area #6624

anveshmekala opened this issue Mar 21, 2023 · 0 comments
Labels
0 - new New issues that need assignment. estimate - 3 A day or two of work, likely requires updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - low Issue is non core or affecting less that 10% of people using the library testing Issues related to automated or manual testing.

Comments

@anveshmekala
Copy link
Contributor

anveshmekala commented Mar 21, 2023 •
edited
Loading

Test type

new test

Which Component(s)

calcite-text-area

Unstable Tests

No response

Test error, if applicable

No response

PR skipped, if applicable

Additional Info

Currently, we determine resizing behavior of calcite-text-area component in e2e test by asserting resize CSS property . We would ideally want to simulate the resizing behavior using mouse operations and determine if resize prop works as expected.

Discussed approach :

  • Get the co-ordinates of the resizing drag handle in textarea and simulate mouse drag .
  • compare getBoundingClientRect values before and after dragging .
  • Iterate the test for different permutations of resize prop value.

Note: This is a draft approach . Find the best possible way to achieve the required behavior.
@anveshmekala anveshmekala added testing Issues related to automated or manual testing. p - high Issue should be addressed in the current milestone, impacts component or core functionality 0 - new New issues that need assignment. labels Mar 21, 2023
@anveshmekala anveshmekala mentioned this issue Mar 21, 2023
Merged
@geospatialem geospatialem added the needs triage Planning workflow - pending design/dev review. label Jan 27, 2025
@jcfranco jcfranco added p - low Issue is non core or affecting less that 10% of people using the library estimate - 3 A day or two of work, likely requires updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed p - high Issue should be addressed in the current milestone, impacts component or core functionality needs triage Planning workflow - pending design/dev review. labels Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. estimate - 3 A day or two of work, likely requires updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. p - low Issue is non core or affecting less that 10% of people using the library testing Issues related to automated or manual testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jcfranco @geospatialem @anveshmekala