Open FrankVisuals opened 4 months ago
hey π - silence for 30 days π€ ... anybody? π
we have some ongoing discussion how to best handle error cases. This definitely falls into that and should err out hard. Will take a look as soon as time permits.
hey π - silence for 30 days π€ ... anybody? π
Is the discussion done offline or can it be followed in github?
Hi @FrankVisuals,
this one of the topics we still have to tackle. In the meantime:
When you just want to check that a control was found you can do something like this:
const app = await browser.asControl({...})
expect(app.isInitialized()).toBeTruthy()
This should really throw an error when the control was not found
hey π - silence for 30 days π€ ... anybody? π
closed π΄ because silencio π€« since an additional 14 days after staleness π
Sadly, this got auto clsoed, is there any update on this?
hey π - silence for 30 days π€ ... anybody? π
Describe the bug
I had this bug open https://github.com/ui5-community/wdi5/issues/501 a few month ago, but it got closed due to inactivity. Now I am facing this issue again - in a fresh project.
I have an expect that is very obviously wrong. I followed to guide to init a new project using
npm init wdi5@latest -- --ts
and this test was generated.I removed the skip and executed it - it works. However, I don't have the namespace
ui5.typescript.helloworld.view.App
in my app. It should fail.I added the line
expect(app).toBeDisplayedInViewport();
in order to try to force a test failure, but as you can see, the error log is coming up, but the test succeeds. This seems to be the same issue I described in #501 - only this time, I have a fresh project running.To Reproduce Steps to reproduce the behavior:
npm init wdi5@latest -- --ts
npm run wdi5
UPDATE:
I've just cloned this repo and adapted the Basic.test.ts in the ts-example app. I rewrote the test to
This should clearly fail, but still leads to success.
Expected behavior The test should fail if the control does not exist.
Logs/Console Output if applicable, please copypasta code-fenced log output, e.g.
Runtime Env (please complete the following information):
UI5
1.120.11wdio
8.39.1node
v18.16.1Additional context
Test was executed non-headless and locally, on my machine