Hi Mike,
Shane is exploring options for automating tests in VS Code and believes we
might be able to get away with a pure TypeScript test suite, which would be
great IMHO. I'll let him talk more about that if he's willing and has the time.
On the topic of code reviews, I think we should
Should the issue be added to the GitHub repository, Apache Jira, or both?
On 5/24/22, 1:15 PM, "Shane Dell" wrote:
From what I am seeing it is common to use mock data to test out extensions.
I can create an issue in apache/daffodil-vscode to start work on a new test
suite for better
>From what I am seeing it is common to use mock data to test out extensions. I
>can create an issue in apache/daffodil-vscode to start work on a new test
>suite for better testing UI aspects and other things that rely on the VS Code
>API.
On 2022/05/24 13:48:46 Shane Dell wrote:
> I think to a
I'm glad the topic of automated testing has come up and I'm hoping we can get
some help in standing it up. I think it would be great to start integrating a
robust front-end test suite as soon as practical for all the reasons stated.
Does anyone have any advice on test suites that would be a
I think to a certain extent we can create more unit tests that test out UI
components. I have not
done much of this but I believe that it is relatively common to do so for
frontend heavy projects.
However, in some cases in may be more involved some cases I have seen they
write python
selenium
Are there test automation tools available that can be used to drive the
vscode debugger?
This would ideally include both something that drives the UI via easily
created/maintained scripts, but also things like code coverage analysis.
I am always an advocate of built-in-self-test and of
