Cross Browser Testing (Checking) Tools
Depending on the project context, you might want consider these tools
for BCT.
·
BrowserShots
·
Adobe Browser lab
·
Browsera
·
Crossbrowsertesting
·
Spoon
·
Browerstack
·
Browsercam
Some of these tools
check compatibility by taking & comparing screenshots of the web pages
displayed across different browser/OS combinations.(Literally a Cross browser
Testing as a Service)
For more details on,
how the individual tools work, please refer their website or contact their
customer support.
In some project
environments, the stakeholders might not be interested in exposing their web
pages to external services due to various business or environment factors.
Just a few examples – Pros &
cons of different tools can be analysed(in detail) based on your project
context)
v Home grown Automation
Suite for BCT
Example –
Selenium Grid to
drive different browser OS combinations in parallel
Automation Framework
to run across different web pages based on scenarios and comparing the
screenshots or working through the browser’s DOM regarding placements of
different GUI elements and comparing their placements with other browsers.
·
Tricentis Tosca Cross Browser Testing (http://www.tricentis.com/en/tosca/x-browser)
·
Smart
Bear Test Complete (http://smartbear.com/products/qa-tools/automated-testing-tools/web-ria-testing/cross-browser-testing-with-testcomplete)
Test build Scope
Depending on your Project context & Development model (waterfall,
Agile), your Execution build scope can be planned.
Example: -
For your Execution Scope for BCT of your application your scope can be
planned something like this,
|
Browser
|
Priority
|
Build 1++
|
Build 2
|
Build 3
|
|
IE 8
|
High
|
Functional (50% of Progression features )and
the relevant user experience
|
Functional (Remaining 50% of Progression
features )and the relevant user experience
|
Bug Testing
|
|
Firefox 11, 12
IE 9
Safari 5
|
Medium
|
High Risk End to End (E2E) Scenarios, Part
of user documentation, Data Management,
Configuration, User Management, Testability
& Pages Covering different Page Templates
|
|
Bug Testing
|
|
Chrome 18
Firefox 3.x
|
Low
|
High Risk E2E Scenarios, Data Handling, User
Management & Pages covering different Page Templates
|
|
Bug Testing
|
|
Chrome 12
Firefox 4.x
|
Low
|
E2E Scenarios & Pages covering different
Page Templates
|
|
Bug Testing
|
++ - Depending on the Project context, build scope might include Regression Test
cases, lesser builds, more Sprints etc.
References
http://mattarcherblog.wordpress.com/2011/11/08/risk-based-cross-browser-testing-with-scrum/
No comments:
Post a Comment