Tag Info

Hot answers tagged

18

Selenium 2 offers both iphone and android testing. They are experimental. http://code.google.com/p/selenium/wiki/IPhoneDriver http://code.google.com/p/selenium/wiki/AndroidDriver


11

One of the nicest directories is official FTP. It's official organized per OS/arch organized per version (including Beta, Aurora and Nightly builds) organized per language However, the FTP directory doesn't have as many mirrors as the official Releases server. Therefore, the FTP directory is great, but if you're going to be downloading many of the ...


9

Research your potential audience. What country are your hits from? Europe is divided between Firefox and IE, USA has significant share of Safari, and users from ex-USSR countries use Firefox, Opera and IE in more or less equal proportions. What is the topic of your website? If it intends for a wider audience, you should pay attention to old or obsolete ...


8

Selenium solves a large part of cross browser testing. 90% I would say. Selenium is good for web testing across browsers. For UI related stuff adhoc manual checks are sufficient. I used to do manual checks to verify look and feel of UI (Text Sizes appearing small in a browser, Alignment Issues) Functional UI testing in selenium across browsers verifies Id's ...


7

To decide what we need to test we need to understand what is likely to break. The current batch of web browsers have a set of commonly known bugs and differences. If you understand these differences, you can go a long way to understanding why pages have javascript issues or render differently in different browsers. Internet explorer has a large number of CSS ...


7

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


7

You're actually creating a second Selenium session in your tearDown() function. You need to put the session created in setUp() into an instance variable, then close that session in tearDown(). class TestFoo(unittest.TestCase): def setUp(self): self.selenium = selenium('localhost', 4444, "*chrome", 'http://blackpearl/') ...


6

Selenium is mostly a functional testing tool. So any issue that you find using selenium will be across all the browsers No, that's not actually the case. Some functionality can be broken in some browsers while working in others. For example, for one of the apps I test, I've seen significant functionality issues going from IE 6 to IE 7 to IE 8.


6

Automated, parallelized, cross-browser testing is a seductive idea, but in my experience, the cost may not justify the benefit. I do not know whether your customer requests are based on actual experience or the advice of a trusted professional or the unfounded claims of someone in an elevator. You may spend a lot of time maintaining your cross-browser ...


5

IE 7 is expensive to support at my company. It is encouraging to hear that Microsoft will force automatic update users to upgrade to IE 8 or IE 9. If you host your own product, you should be able to analyze your web server's access logs to determine the market share of each browser version. With those numbers in hand, you can evaluate tradeoffs between ...


4

In his own inimitable fashion, QA Hates You posted a blog on this very topic http://qahatesyou.com/wordpress/2011/12/dont-base-your-compatibility-matrix-on-a-press-release/ "Nor will it force updates on consumers who have already declined earlier offers to abandon an older IE"


4

A simple JavaScript error might be a reason of a huge bug. I am always having “Show JavaScript errors” turned on my browser. Let’s consider the following situation: During saving a Web Form, some JavaScript exception had occurred while populating data from the UI input fields into internal JavaScript object, for instance, JSON object. In this case, some ...


4

The short answer is that each browser implements the industry standards based on the implementation team's understanding of those standards. There are several different base engines that are used by different browsers, including but not limited to WebKit, Gecko, Trident, and Blink. That accounts for the majority of differences in behavior between different ...


4

My personal experience is with testing iOS devices so I can only refer to those. Your question is broken up into three separate parts so I will answer each of those in turn. I'm thinking along the lines of a Firebug for the iPhone/iPad/Android/BB that can truly give more insight on the markup/scripts. This is supported in iOS6 by enabling the ...


4

I know of no "Industry Standard". And whenever I hear this sort of question, I always think "What industry do you mean?" The testing industry? The software industry? The website industry? The industry that offers an application identical to yours? For your particular website, what kind of zooming do your users do? That's where you should be concentrating ...


4

I believe most computer users in the general population do not install any plugins at all -- especially if you consider mobile users. Personally, I would not do any plugin compatibility testing without explicit evidence of a conflict. By the way, this recommends a way to prevent the Skype plugin from breaking your page layout.


3

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 ...


3

The only sure way is to use virtual machines. Things like IE tester emulate older versions of IE, but they a locked into using the current set of DLL's loaded into windows. You will see errors in the native version of the browser that you do not see in IETester (and things like it). I know this to be a fact because I have previously used IE tester to ...


3

"ShootMe" (Screen Grabber) Allows you take screenshots of your device and also do screencasting up to 30 fps "Log Collector" Collects a device log and sends it to a developer using a method (email, messaging, etc.) of your choice. Both of these are a staple when it comes to testing mobile web apps and can be found in the Andriod marketplace.


3

I searched Google for "User-Agent strings" and found this and this and this. If you work for a company with a website, you might try asking them for a list.


3

I found this site that offers a sample of user agents in csv format: http://user-agent-string.info/download Actual download link: http://user-agent-string.info/rpc/get_data.php?uaslist=csv The format is: "Type","Name","useragentstring"


2

I was going to mention http://www.oldapps.com/category/browsers But for Firefox-specific needs, the official FTP site is best.


2

One thing that many people seem to forget is the information at their disposal. Does the company that the site is launching for already have any sites in production? Is this replacing another one? Is this just an enhancement or bug fix release. If the answer to any of these is yes, ask for (if you don't already have) a copy of the browser (and often ...


2

Critical areas for browser compatibility checks are missing functionalities due to lack of support for javascript in the specific browser. It should also take into account the GUI issues like misalignment. Some of the browsers may not support Javascript or Active-X control which are required by the software to provide the desired functionality to the ...


2

I'm not sure about the API, but something more generic that would work for any browser would be to use a selenium test to execute some JavaScript. navigator.appVersion gives you the browser version.


2

Implementing the same standards will not result in same product. There will be differences. Different teams make different (human) mistakes, use a different architecture, etc... If you search for browser-benchmarks you will notice a great difference in the speed of the renderer and the JavaScript engines. This must prove they are different under the ...


2

Yes, Pages should be tested at zoom level. Because its come under the quality of project. Website quality should not be compromise at any level. User can think in any way. So if on zooming Web pages alignment disturb then its come under bad quality site. We should focus on every point for good quality.


2

I agree with Usman. Your site should be tested at various zoom levels since most browser clients and devices support zooming functionality and your customers may zoom regardless of whether you want to support it or not. One of the primary purposes of testing is to provide information, help identify issues that highlight any disparity between what customers ...


2

It depends on the requirements or what the stakeholders want. Although ideally, zoom levels should be tested since there are users who use the zoom functionality.


2

It appears that NUnit http://www.nunit.org/index.php?p=testFixture&r=2.5 now supports parameterized test fixtures. This may allow you to create a test that will do what you need. This SO answer has a similar question for NUnit selenium tests. ...



Only top voted, non community-wiki answers of a minimum length are eligible