I used VirtualBox to install Window 7 and without updates solved the problem. Thanks all
One thing I notice why IE11 not working in the host computer is under "About Internet Explorer" it doesn't shows the IE version but instead the Window 10 version.
In the working VM, the IE displays the actual version of IE:
I believe this is why it is stuck in the webdriver, something to do with the IE itself.
I'm trying to select a checkbox on the following public webpage using Selenium XPath from Python and click it to change the checked status.
http://simbad.u-strasbg.fr/simbad/sim-fout
For example, the checkbox that I would like to click is located under "Fluxes/Magnitudes" and is named "U" shown in the picture below.
Upon inspection of this page I built the following XPath to select the checkbox:
//*[@type ='checkbox' and @name='U']
This returns what I believe to be the correct element, however when I try to run click() on the object it fails with the exception 'list' object has no attribute 'click'
When I look at the functions for this object in a debugger it indeed does not have a click function. How can this be true for a checkbox? Is there a different element that has to be selected?
Thanks!
We're considering creating automated tests that confirm that specific items made it onto an SQS queue. Note that that sentence said "made" it - this would be a test that can be run on a live system. These tests would be run after changes are deployed to a given environment and the system is up and using those new bits.
From what I've found so far, it appears that AWS X-Ray may be able to look at recent items that made it onto the queue. Is X-Ray a sensical option? Do other, more-effective approaches exist?
Finally, is this a testing approach that tends to succeed in reality? Does strong guidance exist on how to test in a live system?
What is the best way to proceed?
The best way to proceed is to talk to your management and understand future development requirements, budget, business priorities, deadlines etc
Hiring a QA automation Lead to build FW and start implementing tests?
This is recommended only if your responsibilities and the new QA Leads responsibility doesn't overlap. But for startups without knowing the team size there is nothing much to comment on this. You should be able to see the future responsibility of the Lead and the future number of scrum teams that will come up in the organization. Ask yourself the question , what will LEad do after the framework is developed
Hiring QA engineers who are capable of doing manual and automation testing to get both things off the ground and moving?
The main thing here is to priorities the tasks and decide the development to QA ratio. Its applicable to have atleast 1 Test Automation QA engineer per team in your current situation and automate as much use cases as possible and avoid the need of manual teams.
But to keep up with the current development pace have a separate manual Test team with a ratio of 1 manual QA to 2 Teams who work in rotation between teams in manually testing in sprint features. This ensures that the Manual QA are used effectively and are not over or under used (The ratio will change according to project size)
Should I start with building up manual test coverage for the main priority user flows and build out from there and automate after?
In the agile world, manual test cases are waste of time and effort, try to define executable specifications like using gherkin, keyword-driven or have test cases defined as acceptance criteria for user stories
Should I identify Automation test cases from the get go?
Having end to end test automation allows you to avoid need for manual test team in the regression phase , you can use them for adhoc, exploratory and usability testing . THis increases the overall testing efficiency than executing the same manual test cases
So in summary
DesiredCapabilities capabillities = DesiredCapabilities.edge();
capabillities.setBrowserName(BrowserType.EDGE);
capabillities.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
capabillities.setCapability(InternetExplorerDriver.INTRODUCE_FLAKINESS_BY_IGNORING_SECURITY_DOMAINS,true);
capabillities.setCapability(CapabilityType.SUPPORTS_JAVASCRIPT , true);
capabillities.setPlatform(Platform.WIN10);
capabillities.setCapability(CapabilityType.BROWSER_VERSION, "latest");
WebDriver driver = null;
List<String> displayedList = new ArrayList<String>();
try {
System.out.println("STARTED");
driver = new RemoteWebDriver(new URL("url"), capabillities);
driver.get("https://url");
System.out.println("OPENED");
I am getting the below Error:
Exception in thread "main" org.openqa.selenium.SessionNotCreatedException: Unable to create session from {
"desiredCapabilities": {
"acceptSslCerts": true,
"browserVersion": "latest",
"browserName": "MicrosoftEdge",
"javascriptEnabled": true,
"ignoreProtectedModeSettings": true,
"version": "",
"platform": "WIN10"
},
"capabilities": {
"firstMatch": [
{
"browserName": "MicrosoftEdge",
"browserVersion": "latest",
"platformName": "win10"
}
]
}
}
Build info: version: '3.141.0', revision: '2ecb7d9a', time: '2018-10-31T20:22:52'
System info: host: 'VDI-PR-E0042', ip: '10.93.173.183', os.name: 'Windows 10', os.arch: 'x86', os.version: '10.0', java.version: '1.8.0_171'
Driver info: driver.version: unknown
Command duration or timeout: 1.35 seconds
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53)
at org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91)
at org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:122)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
at java.base/java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:127)
at java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:502)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:488)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at java.base/java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:150)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:543)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:125)
at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:136)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:212)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:130)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:143)
at Test.TestRemoteGrid.main(TestRemoteGrid.java:60)
I think the best way would be to have a look at BrowserStack website, they actually answer all of your questions.
However, to point you a bit to the right direction, as of May 2021, BrowserStack offers these products:
Out of these, you will likely be interested in these 3:
because they let you test in desktop, tablet, and mobile browsers on various devices and operating systems. A quick look is this screen, you can see there're lots of options:
Live product is with no automation, probably not what you're looking for right now. Automate lets you execute various scripts (you can choose here, Cypress is also supported). Percy is a visual testing tool, it basically takes screenshots of your web app and compares them against some baseline you feed to it.
Now on to you questions:
Do we have 'record and replay' kind of a setting with BrowserStack
BrowserStack is not a tool that will generate any code, it only runs code that you're provided on devices and in browsers you specified. So if you choose a tool like TestCafe Studio, Cypress Studio, or similar, then you can have record & replay feature, but that's something you prepare locally and only then send it over to BrowserStack to execute that code.
We are also developing the UI automation using Behave + Python and so far we have successfully automated our smoke test suite [Regression is in progress], can we also use the existing selenium scripts with BrowserStack [ I know the answer is YES but this will only cover different browsers and not mobile devices, I guess]
Mobile browsers and devices typically display a page differently than desktop browsers. What usually happens is some elements are hidden in mobile browsers, or some other elements get used. If you've created a script that is tied to a desktop browser, it might be a problem because some selectors will just fail, therefore your whole script will fail. This of course depends on a particular app (which we'r not familiar here), so there's still a chance everything will work smoothly on all platforms, but I'd guess it won't and you'll have to spend time adjusting your scripts.
What you get in the console (a.username) is the CSS selector, if you are using xpath you will need a[@class='username'].
Try something like this
$x("//a[@class='username']")[0].innerText
The $x("//a[@class='username']") will return a list of zero-indexed elements. So [0] will select the first element of that list and so on.
With JMeter you can organize your test plan as follows:
Example test plan outline:
The access token is something you're getting as the result of the OAuth 2.0 authorization code flow
It's not a single request, it's a series of requests which you need to implement somehow:
the options are in:
More information: How to Run Performance Tests on OAuth Secured Apps with JMeter
Since you have Session-Based Test Management, you can use your test sessions data to show your team's testing capacity.
For example:
You can plot the number of sessions your team did throughout time. Downtrends may intigate your team is having problems to keep a steady pace or that your testability has improved, demanding less test sessions for the same results.
Normalizing these data with other team capacity metrics, such as number of people involved or story points (if you can very consistent and mature with them) may make this chart more precise.
You can find more details on James Bach's article on Session-Based Test Management.
Also, Kanban metrics may be useful:
In the end, you can have a cumulative flow diagram. It indicates bottlenecks in a delivery pipeline. You can see below, at 2018-10-01, the In Progress color occupies a large part of the chart. It indicates your team was working in a lot of items at the same time, without delivering to Done. It would indicate you may have a story about people switching focus too often during the day, getting requests from many sources.
More details here.
On a final note: Don't count lines of code or number of bugs. Use any data or chart you have to tell a story about testing. Focus on creating adaptability, optionallity, and experimentation. Identify what issues you have and see coming, and prepare yourself to remove those impediments to good testing. You may identity that you gonna need to put more effort in setting up better code quality analysis, or solve communication issues, or test labs issues. These problems may be solved be hiring people with new skills, or changing focus, or changing roles inside the team. You will know what works best to your particular context by experimenting, throughout time.
