-
Notifications
You must be signed in to change notification settings - Fork 802
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.
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
Migrate FSharpQA suite to xUnit suite(s) #10001
Comments
I find these names a bit confusing Maybe aim for this:
So basically rename "ComponentTests" to "UsageTests" |
My idea was that we test compiler as an "external", separate "component", hence the category "ComponentTests". We already have this project, renaming it should be easy though. |
Should "UsageTests" just be "LanguageTests"? Since that's basically what they are. Tooling tests would go under relevant tooling subfolders anyways |
Keep in mind, that currently, there are not only "Language" tests there, but also stuff like IL verification, Interop, I guess if it falls under "LanguageTests", then I guess, we can have it as "LanguageTests" |
Now covered by #12823 |
We want to migrate FSharpQA tests from a custom runner/solution to a standard dotnet test project(s).
Prerequisite: #10000
The text was updated successfully, but these errors were encountered: