JeremyYao commented on issue #1290: URL: https://github.com/apache/daffodil-vscode/issues/1290#issuecomment-3207358512
From 8.15.2025, @scholarsmate mentioned previously looking into UI tests. These some of these tests required delays of a few seconds. In the CI pipelines, the amount of delay needed may change from runner to runner (and locally, system to system). The results were inconsistent on both the CI and his machine. He also pointed out that Selenium, which the extension-tester uses, is extremely fast and requires slowing down. Is there a way to have it go through a number of ticks instead? @stricklandrbls proposed that at this point, it would be better to write more unit-test like files to test the functionality the code provides. It would be much better to have compartmentalized, testable code. We should avoid putting logic in the display/frontend code. @scholarsmate, mentioned too that changing UI elements may require reworking the code and dealing w/ selenium, further slowing development. @stricklandrbls pointed out we should do most of our testing at the script level and keep the display layer light. It was originally proposed to have the extension utilize a MVC-type architecture in the past but was unable to be architected as much due to timelines. We have good tests for now it seems. @hdalsania, mentioned that manual testing covers a decent amount of UI use cases, but it may not be conclusive. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
