Fix/skills test waitfor#556
Conversation
This workflow generates SLSA provenance files for projects, satisfying level 3 requirements. It includes steps for building artifacts and generating provenance subjects.
Add a security policy document outlining supported versions and vulnerability reporting.
Bumps the npm_and_yarn group with 1 update in the / directory: [ip-address](https://github.com/beaugunderson/ip-address). Updates `ip-address` from 10.1.0 to 10.2.0 - [Commits](beaugunderson/ip-address@v10.1.0...v10.2.0) --- updated-dependencies: - dependency-name: ip-address dependency-version: 10.2.0 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…pm_and_yarn-32e07c5719 Bump ip-address from 10.1.0 to 10.2.0 in the npm_and_yarn group across 1 directory
Bumps the npm_and_yarn group with 1 update in the / directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `vite` from 7.3.1 to 7.3.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v7.3.2/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.3.2/packages/vite) --- updated-dependencies: - dependency-name: vite dependency-version: 7.3.2 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
The test was failing because the Browse tab wasn't guaranteed to exist when queried immediately after render. This fix wraps the tab query in a waitFor block to ensure the component has fully rendered and all tabs are available before proceeding. Fixes the failing test: "surfaces the CLI error in the UI when installSkill returns success:false (issue fathah#310 fix)" The issue was at line 119 where `browseTab` was undefined because the tab hadn't rendered yet. Now using the same pattern as the first test to ensure DOM is ready before assertions.
…pm_and_yarn-c4bc6a0a9e Bump vite from 7.3.1 to 7.3.2 in the npm_and_yarn group across 1 directory
Bumps the npm_and_yarn group with 4 updates in the / directory: [@xmldom/xmldom](https://github.com/xmldom/xmldom), [lodash](https://github.com/lodash/lodash), [postcss](https://github.com/postcss/postcss) and [tmp](https://github.com/raszi/node-tmp). Updates `@xmldom/xmldom` from 0.8.12 to 0.8.13 - [Release notes](https://github.com/xmldom/xmldom/releases) - [Changelog](https://github.com/xmldom/xmldom/blob/master/CHANGELOG.md) - [Commits](xmldom/xmldom@0.8.12...0.8.13) Updates `lodash` from 4.17.21 to 4.18.1 - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.21...4.18.1) Updates `postcss` from 8.5.8 to 8.5.15 - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.5.8...8.5.15) Updates `tmp` from 0.2.5 to 0.2.7 - [Changelog](https://github.com/raszi/node-tmp/blob/master/CHANGELOG.md) - [Commits](raszi/node-tmp@v0.2.5...v0.2.7) --- updated-dependencies: - dependency-name: "@xmldom/xmldom" dependency-version: 0.8.13 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: lodash dependency-version: 4.18.1 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: postcss dependency-version: 8.5.15 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: tmp dependency-version: 0.2.7 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
Added additional system dependencies for the build process.
…pm_and_yarn-a18ae6f8a2
…s.test.tsx The first test was querying DOM elements synchronously before React had finished rendering the tabs, causing `browseTab` to be undefined and the test to fail with "AssertionError: expected undefined to be truthy". This fix wraps the tab selection logic in `waitFor()` to ensure the DOM is ready before querying, matching the pattern already used later in the test for the Install button. The second test already had this pattern correctly implemented. Fixes issue fathah#310 diagnosis test failure.
Greptile SummaryThis PR fixes a flaky test in
Confidence Score: 5/5The core test fix is safe and functionally correct; the duplicate assignment in the second test is dead code that does not affect test behavior or results. The test changes are narrow and low-risk — both test cases still select the correct DOM element and assertions pass. The duplicate browseTab assignment in the second test is inert dead code. Dependency bumps are routine patch/minor updates. src/renderer/src/screens/Skills/Skills.test.tsx — second test waitFor block has a leftover duplicate assignment that should be cleaned up. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[render Skills component] --> B[waitFor: API calls fired]
B --> C{waitFor: Browse tab exists?}
C -- yes --> D[fireEvent.click browseTab]
C -- retry --> C
D --> E{waitFor: Install button exists?}
E -- yes --> F[fireEvent.click installBtn]
E -- retry --> E
F --> G1[Test 1: installSkill called with correct args]
F --> G2[Test 2: skills-error banner shown with CLI message]
Reviews (3): Last reviewed commit: "Merge branch 'main' into fix/skills-test..." | Re-trigger Greptile |
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
parvezmosharafbd
left a comment
There was a problem hiding this comment.
thanks, and always fix upcoming issues.
|
Thanks for tracking down the flaky Skills test. I agree with the core idea here: the first Browse tab lookup should wait for the async render before clicking it. I don't think we can merge this branch as-is, though. It is now conflicting with current Could you please re-cut this as a tiny PR against current For that version:
That should make the actual test fix straightforward to review and merge. |
No description provided.