-
Notifications
You must be signed in to change notification settings - Fork 25
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
[FEATURE] Fix tests and incorporate into CI pipeline #2196
Comments
As a quick update on the current state of ng tests, 163 specs, 65 failures, 1 pending I'm aware that angular is in the process of deprecating karma, however would still be good to get the entire suite passing with karma before trying to migrate to any other test runner to make it easier to identify which issues are legacy and which are migration As as summary of the types of issues see table below
|
Sidenote - table above generated by adding karma-json-result-reporter and manipulating output const failed: Record<string, any> = {};
for (const [suite, spec] of Object.entries(karmaResults)) {
for (const [name, entry] of Object.entries(spec)) {
if (entry.status === "FAILED") {
const [reason] = entry.log;
failed[reason] ??= { reason, specs: [] };
failed[reason].specs.push(suite);
}
}
}
const output = Object.values(failed)
.map((v) => ({
...v,
specs: v.specs.join(", "),
}))
.sort((a, b) => b.specs.length - a.specs.length); Final output converted to markdown using https://github.com/Angular-cz/karma-json-result-reporter |
I've started work on slowly fixing in #2742 |
#2197 includes some fixes to allow the test runner to function for some spec tests. That PR includes the fixes originally included in WIP PR #2080 (now closed).
From #2080:
TODO
Description
Angular has a component and service testing system which is included during new component and service creation, however only partially used for some of the newer services added to the platform.
This PR aims to fix and remove legacy code to allow the testrunner to function, and include any working tests within existing github actions testing pipelines.
https://angular.io/guide/testing
Git Issues
Closes #
Screenshots/Videos
Significant number of test issues to fix
The text was updated successfully, but these errors were encountered: