I am new to test automation. I am using Playwright trying to get my tests to run in GitLab CI. Looking for help with the below error when I click on a drop-down field.
Code
await this.page.locator('dff-drop-down i').click();
Error
retrying click action, attempt #226
waiting 500ms
waiting for element to be visible, enabled and stable
element is visible, enabled and stable
scrolling into view if needed
done scrolling
element is outside of the viewport
retrying click action, attempt #227
waiting 500ms
Works ok when running locally using VS Code, but failing on GitLab pipeline. See the html section for the drop-down field I am trying to clock (https://i.stack.imgur.com/wywJa.png)
click on a drop-down field and expect the field is clickable.
Related
I have configured two jobs on jenkins server. One for creating package and second for deploying package to respective server. And promoted build from first job to second job. Facing issue on upgradtion of jenkins from 2.320 to 2.344. Sometimes promotion status not showing input field for deploy job. I'm attaching images for reference.
Sometime getting following UI on promotion status
Should show everytime:
guys!
I'm running some jmeter tests on Jenkins, and for some reason it stops displaying the results of the last test run and freezes, only displaying results from a run that has been completed berofe, for example, if I start a new run, it will display the results from a previus one over and over again, no matter how many times I run the test suit... Is it any config that I need to change?
Thanks!
I'm using the performance plugin... I was analysing it a bit more and I found out that if a test fails once, this failure will be displayed everytime I run a new test and it's displayed as a failed build by jenkins... In the image, the failed test contains two outputs in the http code, 200 which stands for success and 500 which stands for failed (I believe i'm right).
Jenkins 1.573 / 1.628 or latest version.
Build Pipeline plugin : 1.4.8 (latest)
Till last week everything was OK, today I'm seeing that when I click on the first job in the Build Pipeline dashboard view (to run a process), it used to prompt parameters but not anymore. It's giving me a BLANK white modal window / popup page and there are no input parameters visible.
Any idea! what I may be missing.
http://s000.tinyupload.com/download.php?file_id=03793493629898722609&t=0379349362989872260930671
I had a similar issue, but solution was different. In my Jenkins configuration, the Jenkins URL was not set correctly - it was a http address, whereas my Jenkins was set up with TLS. So make sure that Manage Jenkins - Configure System - Jenkins URL is set correctly.
Finally found the issue.
The issue is either with the Build Pipeline plugin (not using / compatible with Chrome browser) OR it's a Chrome browser issue.
I somehow had Chrome session opened the other day and when I click on "Run" (top section) to start the pipeline / job run, it shows me a BLANK modal window and doesn't show me any parameters.
Version 46.0.2490.86 m
Google Chrome is up to date.
While the same is working in IE or Firefox (I have the latest versions). I guess, I'll use FF/IE for now.
I was able to create the new job but I am NOT able to add any build step.
This behaviour is reproducible and it occurs when I try to do it from the initial “configure” page I get after job creation as well as with a later configure attempt. And its persists for all job types.
It does not depend on whether I am logged in or not.
The problem is that when I open the “add build step” I get a selection of possible job types (“shell script”, “windows batch”, …) but when I select one of those nothing more happens.
I also have other jobs of this type already up and running and I am also not able to add more build steps to those.
I had this with v1.625.3, all of a sudden. Problem in Chrome and FF. Workaround was to use IE.
I've been trying to follow http://devs.valence.desire2learn.com/2013/02/15/remote-plugins-the-bookwidget-sample-2 to make sure we can get the demo running before continuing with development, however we've run into the problem where the sample instructions given don't mention a "System Test Link", and d2l won't allow us to create the widget without one.
What is this, and how can this be solved?
Edit: The system the client is using is 10.1
Looks like the "community" decided that my additions to Sarah-Beth's answer were not appropriate. So here's my edited answer in it's entirety:
The System Test Link is not a required value in order to create a new Remote Plugin. This behavior has been verified against both Desire2Learn 10.1 and 10.2 environments.
A System Test Link value is required in order to run automated tests using the Test button on the Create a New Remote Plugin form. If you click the Test button without populating that field, you will be alerted that a value must be entered in the System Test Field in order to proceed. But this alert does not prevent you from creating your Remote Plugin by clicking Save.
The only required values for a new Remote Plugin are a launch point, a name, and a build type (course builder, widget).
Note. The UI for this management tool can be a bit confusing. When you enter your information and click Save, the tool's UX prompts the browser window to reset to the top of the displayed page: if your browser window is not long enough to contain the entire form, you will not see the little message above the Save button that tells you your configuration has changed, and there's no apparent change in the form's state. Accordingly, you may think that you haven't saved anything when, in fact you have.
Provide the config for your plugin, ensure you have a launch point, a name, and a build configuration selected (at least), and click Save. Once the browser resets the viewport to the top of the form's page, you should be able to click Cancel to back out of the form and see your new plugin in the list of plugins.
We are aware of the discomfort in this form and are taking steps to improve it's UX.
The System Test Link is not a required value in order to create a new Remote Plugin. This behavior has been verified against a Desire2Learn 10.2 environment.
A System Test Link value is required in order to run automated tests using the Test button on the Create a New Remote Plugin form. If you click the Test button without populating that field, you will be alerted that a value must be entered in the System Test Field in order to proceed. But this alert does not prevent you from creating your Remote Plugin by clicking Save.