Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I am using jmeter OS Process to execute my selenium script. If I ran my python script individually, it will pass. The issue is when I put it in threads of 10 some of them failed. My question is does selenium need to "see" the screen to locate the element? From multiple threads, screens pop up very quickly, I think sometimes the first screen is not fully loaded and the next thread/Screen will pop up and cover the previous screen. I think that is why some of them failed.
Selenium does not need to "see" the screen to locate elements. That is the basic principle behind headless tests. A browser (headless, visible, or otherwise) creates a representation of the page in memory: a DOM. Selenium is then able to interact with that representation using the WebDriver.
In all likelihood you need to make generous use of Waits in order to have your tests run correctly.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am in the stage to find out what is Selenium. Its website looks very old. Here is a nodejs version of it.
I also found a good in browser testing solution protractor.
Are they designed to do the same thing? Which one should I use? Why Selenium website is so old, out of favor?
All tools you mention above like protractor, nightwatch are all based on selenium. If you are looking for a nodejs based solutions you can either directly use WebDriverJS (popularly known as selenium) or use many other frameworks which are developed on top of it. Every framework below offers unique features, you need to pick what works best for you. The basic advantage of using framworks is that they do most of the heavy lifting for you, that way your code is small and maintainable. UI testing is hard, the smaller the code you have the easier it is to maintain
protractor (good support if your app is angular)
nightwatch
nemo
webdriverio
wd
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 7 years ago.
Improve this question
On the web application i am currently working on, there is a button. When i click on that button using selenium IDE, IDE doesnot record the click. I clicked the button using button id/css/xpath, it clicks on it but doesnot get to the new page that it is supposed to. However it manages to complete the next scripts and passes the test.
I used Selenium Advanced UI Interactions to click on the button.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
What are the requirements for User Interface testing using Selenium IDE?
I have to test a login page. Do I have to write a UI map file for this?
How can I implement the file in the IDE?
Selenium IDE is a Firefox plugin , so only requirement is having a compatible version of firefox , and you could use the tutorials given by "sircapsalot"
Additional Notes -
1)As far as I know UI Map is a part of Coded UI and not a concern in Selenium IDE .
2)From personal experience I think Using Selenium Web driver over Selenium IDE would be a good choice for having maintainable robust test framework in long term
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am testing infinite scroll feature of my web application on a variety of pages. What aspects should I keep in mind?
What should be automated, using WebDriver for example.
The website is primarily targeting iOS/Android devices.
I would recommend NOT automating any UI feature, at least the visual part. I have found that testing functionality is fantastic with WebDriver, but that UI is harder, and generally not useful with automation.
For example, you could write a test that scrolls the page down, and verifies that new content is loaded. However, you would have no idea whether or not the layout of the content is any good, or even if its on the part of the page you are looking at, unless you thought of each possible scenario where the UI could be wrong, and you tested for each.
That being said, I would still use the UI to make sure it functions. I would scroll down the page, and click on a link to make sure that that link works. Rather than going to a URL, I would use the menu at the top.
In summation, I would test that the features function properly, but not test that the look good. That should be done in manual testing.
For UI testing (design) you can try Sikuli
Here is Sikuli Api you can integrate with WebDriver
Only issue is that Sikuli is not testing picture pixel by pixel... try it and you'll see PROS and CONS
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I am new to software testing and was wondering which is the correct way to test content of a web page. For ex. on a web page if there are 10 labels then should I test first header "Selenium Training and Video Tutorials" and then second details given below the header then further details in this way and create separate test step for testing different text? Or I can use div tag which will give me the complete content of the page at once and test everything in one step. I can do it in one step or divide into steps but I want to do it in a correct way. I am using selenium webdriver (java).
Adding to the arran answer, it is better to split the 10 labels into 10 assert statements so that you can easily know which one went wrong, and also use TestNG or Junit for assertions. Since you are new, there are methods in TestNG like
assertEquals(char actual, char expected);
So in your code, it might look like
header1="programatically get the value using selenium"
assertEquals("Selenium Training and Video Tutorials", header1)
Testng also gives you clear report too.
Writing separate tests for each label as described by you will be a great option for :
increasing understandability
tracking down any errors
fixing of the script (if required in future)