Cypress - Overlay not popping up when button is clicked - react-native

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?

Related

Safari Web Extension icon does not open popup from the overflow (>>) menu

Video showing the bug: https://www.youtube.com/watch?v=tQoOYWe0jfE
Install any Safari Web Extension from the Mac App Store (e.g. DuckDuckGo Privacy Essentials, Bitwarden Password Manager).
Resize the Safari window until the extension browser_action icon is forced into the overflow menu (>> at the far right of the toolbar).
Open the overflow menu and click the menu item for the extension. Nothing happens.
This even occurs when using the sample extension "Sea Creator" developed by Apple. You can build it and try it out by following the instructions on this page: https://developer.apple.com/documentation/safariservices/safari_web_extensions/developing_a_safari_web_extension
I have filed a Feedback Assitant report for this issue: FB9495287 / http://www.openradar.me/radar?id=5035732439662592
Anyone know what's going on here? Or does anyone have a workaround to get the extension popup to appear when invoked from this menu?

Debugging background scripts in safari extension

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.

thucydides report from jenkins not opening properly in chrome where it open in iexplorer?

After a successful run in jenkin a mailer is triggered which contains a thucydide report link.When clicked on the link it open in my default browser i.e. chrome. But it not opening properly the pie chart is not getting displayed and all the test are green.
Can i change some setting to get it properly?
I want it to open it correctly in chrome n Firefox. As both displays similarly.

Problems with testing Bootstrap modal windows with Codeception

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.

Prevent Chrome debugger from stealing focus in React Native

I use Chrome Debugging and Live Reload to debug React Native applications.
Whenever you save a file, the Chrome screen reloads and in doing this, gets focus. This is annoying. Is there anyway to disable this focusing behaviour?

The Chrome debug page is opened by the launchChromeDevTools.applescript script in the react-native package.
You can disable it grabbing the focus by opening this file in your project:
./node_modules/react-native/packager/launchChromeDevTools.applescript
and commenting out the activate line by inserting -- in front.
(This annoyed me enough to hunt down how to do it; it might be worth filing an issue on react-native to make it an option).