wu-sheng closed issue #11574: [Feature] Proposal of the e2e testing of UI
URL: https://github.com/apache/skywalking/issues/11574
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
wu-sheng commented on issue #11574:
URL: https://github.com/apache/skywalking/issues/11574#issuecomment-1837224833
Close as no update for 2 weeks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
Fine0830 commented on issue #11574:
URL: https://github.com/apache/skywalking/issues/11574#issuecomment-1820464759
Glad to see this discussion. It is a good practice to use both unit tests
and E2E tests in front-end development. These two types of tests serve
different purposes and focus ar
wu-sheng commented on issue #11574:
URL: https://github.com/apache/skywalking/issues/11574#issuecomment-1820355532
@Fine0830 What do you suggest on UI side test? You mentioned once.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
LinuxSuRen commented on issue #11574:
URL: https://github.com/apache/skywalking/issues/11574#issuecomment-1820351963
I agree with you that the component test seems is valueable than the e2e
testing. But I'll try to explore if there is a way to make it be easier to
write the UI e2e code.
-
kezhenxu94 commented on issue #11574:
URL: https://github.com/apache/skywalking/issues/11574#issuecomment-1820341754
Tests are always nice to have but adding E2E tests in skywalking-booster-ui
doesn't seem to add many benefits in SkyWalking, the SkyWalking UI is mostly
for displaying data a
LinuxSuRen opened a new issue, #11574:
URL: https://github.com/apache/skywalking/issues/11574
### Search before asking
- [X] I had searched in the
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no
similar feature requirement.
### Description
