It depends on your user base. Either check your statistics or do market research. W3schools shows that IE11 is still 0.4% of their population Netmarketshare says 5.5%.
I once had a client that used an older version of internet explorer on their terminal stations in their physical stores. We asked an extra yearly fee (100k dollars) to test the application ...
Older IE is still widely used in corporate networks since it has more integration with windows security and networking mechanisms as well as with ms office suite.
Big corporations often have large lag in new technologies adoption since they would need to test numerous corporate applications for compatibility with new browsers.
So I wouldn't exclude from ...
It really depends.
Actually rendering elements in a webpage/application and the webpage/application itself depends a lot on the environment it is being accessed. The environment includes, the OS, Browser, any plugins in the browser, the device screen size, the interface mode of the device, the technology you used to create the webpage/application and more.
IE is (unfortunately) still around. It is not unusual for large government companies to have a deal with their hardware/software vendor that specifically mentions Microsoft products, including IE. They often require all their software to be compatible.
Government organizations, by inertion, will continue using IE until the contract runs out and they all get ...
This Stack Overflow thread suggests that there are differences and the modes are not totally accurate.
Depends on your definition of risk and how accurate the results have to be for you and your stakeholders
As shown in the other answers, it really depends on your user base.
If you are targeting developers and high-end users, you probably won't have many (or any) using IE.
If you are targeting corporate or government environments, many may still be using IE (or obsolete versions of Chrome). Any update of the browser used by default on user's computers may break ...
Yes , I have tested a responsive site into the Different browser.
In Google Chrome Browser to test the Responsive view press F12.-> Click on 'Toggle Device Mode' , Using this option we can select the different type of device mode.
Another option is we can add app which is "Responsive Web Design Tester", using this on right click menu Responsive Web Design ...
TL DR: Establish a baseline, tinker, and react.
In general developers should not worry too much about cross browser testing. Yes, it's a problem, and yes, they need to be aware of it, but I would keep it to a minimum. Let them focus on great functionality first, and not that developers shouldn't care about quality (because they totally should!) but in ...
Multi-device/browser testing strategy
Above all else:
Know your user population and the devices they use and the way they use them
Determine if your focus is manual or automation testing as they have different requirements
Find out what browsers, devices & versions are used by your users (server logs, new relic, etc.)
Ask the business what percent of ...
Until a few weeks ago I would have said "maybe", because people who are still using Windows 7 and don't want to install a non-Microsoft browser (for whatever reason) were stuck with IE11, and couldn't install Edge. They probably make up the bulk of the 0.4% IE users mentioned in another answer.
But recently Microsoft has created a new version of ...
One of the disadvantages of using SaaS for regression testing is that you need to allow outside organization access to your pre-production test environment. In most organizations, it has significant part of real production information, which can be security risk.
Even if you de-identify user data (scramble addresses, phones, names etc) in pre-production ...
Managing multiple browser setups on a single machine sounds like a nightmare.
Also I wonder how many browsers you really need to support, have a look at Browser market share per version.
I think services like:
Are better suited for your browser ...
Chrome JS Profiler
Firefox JS Profiler
A good code profiler (JS or not) will tell you who started what function call (stack trace or call tree), how long the particular function was running and ...
Sadly, years of playing with emulators of one form or another has taught me a very simple lesson:
There is no substitute for testing your software on it's target
No matter how good a simulator or emulator you are running, there will be enough situations that the sim/em-ulator doesn't cover 100% accurately that you are leaving potential problems
I've also ...
I think the general answer is "be reasonable". Just because you're doing blackbox testing doesn't mean you should do extra useless testing--in this type of situation, you're likely better off looking at how the code is implemented and deciding on the scope of testing accordingly. I've seen too many blackbox tests that were long and painful to execute but ...
You can search around for browser statistics over the Internet. As an example here is the stats provided by w3schools.com based on over 45 million monthly visits.
NB! The table captions are clickable so that you can drill into the details of particular browser version stats.
The answer is that
They don't test on all of the combinations
They focus on the ones that are used the most
For example there are literally thousands of Android devices and sizes and OS versions. So no company is testing ALL of them. Similarly, companies may agonize over testing ie6 vs ie7 vs i8 vs i9 is 2017 but none that I can imagine are still testing ...
There will be differences between emulators/simulators and actual devices. Android emulators just emulate the screen size and pixel ratio and run a stock version of Android. Many of the major devices run their own custom version of Android. For instance, any Samsung Galaxy runs it's own version of Android which contains Samsung software to promote people ...
Docker is not a virtualization platform. It is a containerization platform. It just isolates applications from each other. It might event fail to run the image that is built for one version of Linux within another version of Linux (for example 64-bit vs 32 bit).
So if you need to test the back-end there is no other ways except virtualization. You can either ...
Microsoft bids farewell to Internet Explorer.
As per latest information from Microsoft, Microsoft To End Support For Its Ageing Browser Internet Explorer In 2021(News here).
But still most of the client required the Internet Explorer. Because they are still using the Older version due to some reason with security integration with Microsoft tools.
Have you tried having a look at Selenium or what is now called Webdriver (Selenium2)?
You can use the Selenium IDE to record your tests on Firefox. However after the tests have been written they can be converted to other languages such as C#. Java. Once that is done its quite easy to get the same test to run on Internet Explorer, Chrome, Mobile browsers, ...
A lot depends on what you want the front-end automation to do.
Given that you've got a lot of web forms with code behind, I'd honestly consider starting with the unit test framework built into Visual Studio, and using that to test the data handling (I'd recommend taking a look at Channel9's TechEd videos for an idea of what you can do with Visual Studio ...
I assume your web application is for external customers (so your users can use web app in many browsers and operating systems outside of your control). Which is very interesting challenge - exactly what we are doing :-)
You are excellently positioned to use new future W3C standard for browser automation, Selenium Webdriver (Se 2). (In a way, you future-...
This is a good question with no "right" answer as a great many factors come into play and the right answer depends on your individual situation.
Factors to consider are:
developer group size
company size and resources
current browser usage of your software
developer uniformity of local browsers ...
We've gone through a very similar process over the last few years and I can share some things that have worked for us.
What to Test
There are a lot of facets to web apps and there's a lot of benefit in testing behind-the-scenes code, but the best place to start is usually the web interface (so browser automation tests). This will help you identify where ...
Where I work, there are three web applications that need to be maintained, with a fourth (which is intended to unify all three existing applications) in development. Each has a distinct purpose:
Application 1 is an enterprise-level employee and payroll management web application used by both internal payroll specialists and externally by customers.
There are online services that provide access to older browser versions (Chrome, Firefox, IE, ...) like testingbot.
To download older versions of Chrome, try this URL: http://commondatastorage.googleapis.com/chrome-unsigned/desktop-W15K3Y/$version/win/chrome-win.zip
After working on this for a few hours with a colleague and doing some in-browser debugging in Safari we came to the following conclusion:
The element was not visible ('below the fold') and Safari was not able to find the element to then click on.
The solution was to scroll to the area of the page where the element existed
by finding a nearby element ...