scriptoriumadmin/openpetswithchatandmcp
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions
openpetswithchatandmcp/website/test_out.log
OpenPets Dev 65ac83849e Add 'website/' from commit '966aea480ffe1c340553aa878def30131d2af827' 
git-subtree-dir: website
git-subtree-mainline: 8d3849caea
git-subtree-split: 966aea480f
2026-06-17 20:48:39 +00:00

3.3 KiB
Executable file
Raw Permalink Blame History

 
> scriptoriumai-ui@2.0.0 test
> vitest src/__tests__/Runboard.states.test.tsx -t shows explicit blocked readiness reasons --run
 
 
RUN v1.6.1 C:/ScriptoriumAI/scriptoriumai-ui
 
[baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D`
stderr | src/__tests__/Runboard.states.test.tsx > Runboard surface states > shows explicit blocked readiness reasons for compare-route actions when no route-matching run exists
⚠️ React Router Future Flag Warning: React Router will begin wrapping state updates in `React.startTransition` in v7. You can use the `v7_startTransition` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_starttransition.
⚠️ React Router Future Flag Warning: Relative route resolution within Splat routes is changing in v7. You can use the `v7_relativeSplatPath` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_relativesplatpath.
 
Γ¥» src/__tests__/Runboard.states.test.tsx (12 tests | 1 failed | 11 skipped) 78ms
Γ¥» src/__tests__/Runboard.states.test.tsx > Runboard surface states > shows explicit blocked readiness reasons for compare-route actions when no route-matching run exists
→ expect(element).toHaveTextContent()
 
Expected element to have text content:
Wait for route run or refresh
Received:
Run next step: Refresh runs or wait for a route-matching run to arrive.
 
⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯
 
FAIL src/__tests__/Runboard.states.test.tsx > Runboard surface states > shows explicit blocked readiness reasons for compare-route actions when no route-matching run exists
Error: expect(element).toHaveTextContent()
 
Expected element to have text content:
Wait for route run or refresh
Received:
Run next step: Refresh runs or wait for a route-matching run to arrive.
Γ¥» src/__tests__/Runboard.states.test.tsx:169:105
167| expect(within(actionsPanel).getByTestId('runboard-compare-remediat…
168| expect(within(actionsPanel).getByTestId('runboard-compare-remediat…
169| expect(within(actionsPanel).getByTestId('runboard-compare-remediat…
| ^
170| expect(within(actionsPanel).getByTestId('runboard-compare-remediat…
171| expect(within(actionsPanel).getByTestId('runboard-compare-remediat…
 
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯
 
Test Files 1 failed (1)
Tests 1 failed | 11 skipped (12)
Start at 13:05:30
Duration 1.53s (transform 243ms, setup 71ms, collect 369ms, tests 78ms, environment 445ms, prepare 65ms)