โ06-08-2022 7:51 AM - edited โ06-08-2022 7:51 AM
โ06-08-2022 10:18 AM - edited โ06-08-2022 10:19 AM
My Entry with a minimal app to pass tests for week1, nothing fancy ๐
https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/7
โ06-08-2022 4:40 PM - edited โ06-08-2022 4:40 PM
I also submitted my entry for week1, who can guess what kind of app I am planning to build? Any golf fans out here? โณ๏ธ๐๐ผโ
https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/8
โ06-09-2022 10:56 PM
My pull request is ready after passing all the tests, all in green!
https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/9
Thanks!
โ06-10-2022 6:11 PM
New pull request,. Thanks for your suggestions @nicoschoenteich
https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/11
โ06-10-2022 10:46 AM
โ06-10-2022 9:23 PM
โ06-11-2022 6:59 AM
โ06-11-2022 2:56 PM
Here is my Pull Request for my very simple ui5 app. ๐
https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/17
โ06-20-2022 1:37 PM
โ06-11-2022 5:01 PM
Hi colleagues! Thanks for the great challenge ๐
Please, find my entry here: https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/16
โ06-13-2022 10:09 AM
โ06-15-2022 12:53 PM
Hi,
We can use the same pull request right?
Is there a way to reduce the output of npm run ci-tests? Loglevel in config did not seem to do much,
As a wish for the next week I would prefer some test cases which are more Fiori Floor Plan oriented. In week 2 the additional Button to navigation is not really best practice if we start with a list ๐
โ06-27-2022 9:54 AM
Hi there!
Sorry for the late reply.
Yes, you can use the same PR.
There are two places in the wdio.conf.js where you have to set the logLevel (one global config and one wdi5 specific), make sure you set them both to 'silent'.
Thanks a lot for your suggestions and feedback. You are right, the app we are building here doesn't follow best practices. It was more important to us that it was 'easy to start with' and that people would get familiar with wdi5 in the first place, and I think that was achieved ๐
โ06-14-2022 1:45 PM
โ06-15-2022 10:32 PM
โ06-23-2022 6:19 PM - edited โ06-23-2022 6:20 PM
Updated for week 3... not sure where this thing is going. I hope to see some back & forth navigation testing for duplicate IDs ๐
โ06-14-2022 2:30 PM
โ06-14-2022 3:29 PM
โ06-21-2022 7:11 PM
โ06-22-2022 9:25 PM
โ06-15-2022 3:07 PM - edited โ06-15-2022 3:08 PM
I wouldn't use control.firePress() to simulate a user click. Some controls expect parameters in the firePress internal UI5 method. Why not using .click instead and let UI5 fill these parameters ?
โ06-15-2022 3:18 PM
โ06-27-2022 10:06 AM
Hi @ArnaudBuchholz, good idea, thanks for the suggestion. There is also a press() method provided by wdi5 that calls click() under the hood so you can use it on combination with wdi5 selectors (see wdi5 documentation). I will keep this in mind for future projects ๐ค
โ06-17-2022 1:37 PM
โ06-22-2022 10:15 PM
โ06-24-2022 1:07 PM
โ06-29-2022 6:44 AM
Week 1,2,3 https://github.com/SAP-samples/sap-community-code-challenge-ui5/pull/40
I have idea for the next challenge. It is a Typescript in Sapui5. Maybe it will be interesting for me and some community members(I think)
โ06-29-2022 8:29 AM
Hi @former_member5334, definitely a great idea. More content on TypeScript in UI5 will come in the future ๐ค
โ06-29-2022 12:07 PM
โ06-29-2022 4:17 PM
โ06-30-2022 9:46 PM
โ06-30-2022 9:12 PM
Week3 test "should have button that opens dialog" sometimes passes and sometimes fails. I use fragment and load the fragment asynchronously.
https://github.com/miyasuta/sap-community-code-challenge-ui5/tree/week3
โ06-30-2022 10:28 PM - edited โ07-05-2022 9:45 PM
For week4 test, I'm writing the following code, but I sometimes get "navButton.firePress is not a function" error. Same again, sometimes pass, sometimes fail...
it("Should go back to main page", async () => {
const navButton = await browser.asControl({
selector: {
id: "navButton",
viewName: Detail._viewName
}
})
await navButton.firePress()
const url = await browser.getUrl()
expect(url).toMatch(/.*\/index.html#*$/)
})
My week4 code here.
https://github.com/miyasuta/sap-community-code-challenge-ui5/tree/week4
โ07-06-2022 7:17 AM - last edited 2 weeks ago
I have the same issues you've described. I had to add this "dummy" test with the browser title to give it some timeout.
As I've seen in the browser, detail page doesn't have enough time to be opened. Looks like await Detail.open() doesn't actually wait until the page is fully rendered.
โ07-06-2022 4:14 PM - edited โ07-06-2022 4:15 PM
Hi @Former Member and @MioYasuatke,
I also observed something similar a while back (https://github.com/ui5-community/wdi5/issues/259). Can you maybe try and remove id="app" and see what happens? Would be interesting to see if this is the same issue.
โ07-06-2022 9:20 PM
Hi @nicoschoenteich ,
Thank you for your response. I have tried removing id="app" from App.view.xml, but as my Main view is embedded into App view, this broke navigation and the page is not properly displayed.
โ07-07-2022 10:56 AM
โ07-07-2022 7:00 AM - edited โ07-07-2022 7:01 AM
Hi @nicoschoenteich, I've tried that, but it also broke the app navigation.
I think I found what's wrong: should we add await here? https://github.com/SAP-samples/sap-community-code-challenge-ui5/blob/main/webapp/test/e2e/pageObject...
โ07-06-2022 9:41 PM