I have a written a intern functional test which copies data from one cell and pastes it to another cell. The problem is every time run the test and copy the data I get a dialogue box with the message
Pasting from clipboard is
currently turned off by your browser.Local Data will be
used
Now because of this popup my functional test freezes and everything else starts to fails. Luckily to avoid this there is a way. .acceptAlert()
.copyfunction()
.sleep(500) //wait for popup
.acceptAlert() //first attempt to copy after login causes alert about using local memory
.pastefunction()
Although this works locally there are times the test still fails when in jenkins. Its not stable. How do I make it stable.
Related
I'm new to selenium. Currently trying to automate the testing process of a react Django based app using selenium script recording in selenium IDE. I'm facing repeated issues in mouse click parts.
After i record the process and run it, it breaks in a mouse click script. My testing software have a create, update and delete function. most probably the error comes in clicking the update and delete button. So, right now i'm using Tab button to reach update and delete button which is a little time consuming in the recording process.
The above given image is where i get the error
The below is the log of the error
Is there any way to overcome this issue or any way to change the script on the error part to make it right.
Also, it would be kind if you suggest me any other best way to automate testing of my react application other than this way.
I have a moderately complex script (create about 20 different tables, approx 1500 lines). When making changes, I only need to run the part of the code that comes after the change. I normally dont have any issues with this, but today, I selected lines 800-1500, hit ctrl + enter, and when it completed the run 6 minutes later, I found that all of the code above the line I started the run from (ie lines 1-799) had been deleted.
When I hit ctrl+z nothing happens, so somehow the change has been locked in. I have some earlier versions of the script, but there are changes in here that got deleted that I dont have saved anywhere else.
Two questions:
why is this happening? any way to prevent it from happening again? (other than stricter version control, or running the subset of the query in another query editing window)
Any way to recover the deleted code if ctrl+z doesnt work, and it's not in the query history as I didnt run that piece of it today?
notes: using BigQuery web interface for this
Something caused your browser tab to reload itself. The URL in the browser immediately updates itself with a new job_id parameter every time you execute a query, and going to that URL (via reloading the tab or otherwise) will display the exact SQL executed by that job and the resultset if the job has finished. If you've only highlighted a portion of the query -- welp, that's the query that got run so that's the query that will be displayed when you revisit that url. :(
The new "editor tabs" feature has been causing this for me: I have to click the "disable editor tabs" button at the top of the bigquery UI to prevent the page from reloading when running queries with multiple stages. But there are an endless number of possible reasons that your particular tabs might be reloading on your particular system, so here's a second fix:
Use /* */ SQL comments to block off the parts of the query that you don't want to run. The comments are part of your query and will therefore still be visible even if the browser tab reloads.
I'm trying out FuncUnit with a simple login/logout script for an app, using Chrome on Windows 7. I've noticed that both the speed and reliability of the test differ depending on if the test is running in the currently selected tab in Chrome.
If the tab isn't selected, the test runs quickly and without error. If the tab is selected, text is typed slowly and sometimes incompletely (so only half the password will be typed before the submit button is clicked), clearly visible elements fail to be found and the test has about a 50% success rate.
Am I missing something here? It's proving less reliable than even QTP unless I deliberately deselect the loaded tab and I'm dubious about any automated test that needs user interaction to pass reliably.
Turned out to be a Chrome version specific issue
I'm using Selenium IDE to test our website/application. I have noticed that there are specific fields on which Selenium gets stuck. At any test speed, when Selenium gets to that field in the testing it gives out the error that it cannot find the ID. But then I double click on the test line it then goes through. In other words, Selenium IDE can find the ID when I double click on the test line, but not when it is automatic.
Moreover, it is always with the same specific fields. 95% it finds, but a few it gets stuck on in automatic mode.
Also, something similar. I have a specific page where you type data into a series of textboxes. For those specific textboxes it always skips a few of them when in automatic mode. No problem when I double click it. Only when automatic. But all other textboses are fine.
And this occurs even at the slowest speed.
Thank you.
Please when i choose "Release" in configuration manager and try to open my program exe and work in it , A message box with "myprogram has stopped working .." , This happens just when release mode is choosen but debug mode, the program runs fine and no problems !
my program contains datasets and connections and more , all are about working with database access
Note: that message box dosen't appear when start my program , it appears after start and when open and close a certain forms
i cant put my code , it is very big about 1000 lines but i'am using this simple code to show a certain form :
Dim o As New commandsSearch
o.ShowDialog()
o.Dispose()
i think it is a memory problem , maybe?
please give me your solutions :)
Thanks.
Sometimes this can happen when you make initialization calls (using new) in declarations. If there is an error during initialization, the messages can be generic at best. Try temporarily commenting out classes, etc., that are created before the initial form has been loaded, a few at a time, until you narrow it down (or eliminate it as a possibility).