I'm having a little trouble testing the appearance of modal windows with a website I'm helping to build. These modal windows are used to fill out forms and I'm writing tests to test if they appear and later to fill them in and test the submit functionality.
I'm using Codeception with the WebDriver module to test and frequently there are errors when trying to waitForElement with the modal. It doesn't always result in an error though, sometimes Codeception seems to see the modal and other times it doesn't.
I'm wondering if there is a better automated testing framework for testing Twitter Bootstrap modal windows or if I'm just not doing something right.
Related
I have a nuxt ssr application. I want to test render time of application. Are there any methods or tools for test that?
You can use Lighthouse on chrome, there is also a Firefox version too. First make sure you run the the app in build mode(npn run build > npm run start). Testing it in development mode will take too long and results will probably be inaccurate.
Go to the lighthouse tab in the inspect tool and click "generate report". It will produce a report like in the below picture. Click the "View Original Trace" button.
There you can see the render time and other benchmark results in detail.
Description:
I am currently trying to write an automated test that involves clicking on a button within a navigation bar. The expected behavior is that an overlay that contains more links would pop up, as seen in this video here: https://www.screencast.com/t/55vkmhY8msjt
When testing this manually within a Chrome browser (which is recorded in the aforementioned video), the overlay pops up as expected.
But when executing the automated Cypress test within the Cypress browser, Cypress is able to locate the element and successfully click it, but the overlay does not pop up.
When I manually click on the button within the Cypress browser, the overlay does not pop up.
Video of bug being reproduced:
https://www.screencast.com/t/iSn8suNHa
It's hard to tell, but after the test execution finishes, I am manually trying to click on the button with my mouse.
I've tried several things:
cy.get(selector).click({force:true})
cy.get(selector).trigger('click')
cy.get(selector).invoke('click')
Extra information:
This button was recently re-implemented using React Native's TouchableWithoutFeedback
There are no errors being thrown in Cypress, no errors in the console.
Versions
Cypress 7.5.0
Chrome Version 90.0.4430.93
Can somebody please suggest some other steps I can try?
I'm writing automation tests for Electron application using Java->Selenide (Selenium)->chromedriver 83.
I can successfully get access to visual elements of the app using xpath locators. But currently I need to check that window of my app is minimized after pressing "Minimize" UI button.
I can't find any easy ways to check that window is minimized from chromedriver.
May I use Electron API to get property win.isVisible or something like that? Or maybe any other ways to check that window of the Electron app is minimized?
Thanks
I am working on a custom Safari extension and would like to debug the Background scripts. I am not certain how to do this? Ideally, if there was a way to step into the background scripts, that would be great. But when I try to step into a background call, the Safari debugger just steps to the next line. The console.log within the background scripts do not get printed to the console (This is the console I launched from right clicking a popover that is part of the extension and then hitting inspect).
Any help on this would be great. Thank you.
This is an old question that asks about a different type of Safari extensions but I figured it could be helpful to add an updated answer now that Safari (v14) supports the Web Extensions API (similar to the API that all other major browsers use).
Debugging background scripts is now built into the Safari menu in the toolbar: "Develop" => "Web Extension Background Pages" => select your (enabled) extension. That should open the dev tools with all your background scripts where you can set breakpoints, check the network tab, etc..
As a side note, you can debug your extension's popup by opening it, right clicking the popup and clicking "Inspect Element".
In case this comes useful for someone - I figured out a way to view console statements in the background scripts. Open the extension builder and click on Inspect Global Page. Go to the console tab and the console.log messages in the background scripts will be printed in that console.
Now you can use Safari Preview to debug your Safari App Extension. There is a control to select the extension container at the lower-right corner of the console.
I want to know why in WEBVIEW Context the xpath generated by Appium isn't working using iOS simulator with java to write our scripts?
Other question is there a way to make the code generated by appium recorder working in our java classes, because for now while we are in WEBVIEW there is no chance with appium we have to take a look into html code to create code.
PS : I have already tried to change the context to NATIVE then turn
back to WEBVIEW_1 but no changes.