The term “cross-browser functional testing” usually means some variation of automated or manual testing of a web-based application on different mobile or desktop browsers. The aim of the testing might be to ensure that the application under test behaves or looks the same way on different browsers. Another meaning could be to verify that the application works with two or more browsers simultaneously. Malcolm Isaacs examines these different interpretations of cross-browser functional testing and clarifies what each means in practice. Malcolm explains some of the many challenges of writing and executing portable and maintainable automated test scripts which are at the heart of cross-browser testing. Learn some practical approaches to overcome these challenges, and take back manual and automated testing techniques to validate the consistency and accuracy of your applications—whatever browser they run in.
Malcolm Isaacs
HP
Malcolm Isaacs is a member of the functional architecture team in HP Software’s Application Lifecycle Management group, focusing on best practices and methodologies across all aspects of the software development lifecycle. During the course of his career, Malcolm has worked in various positions including software engineer, team leader, and architect. In 2003 he joined Mercury (later acquired by HP), where he worked on a number of products which specialize in supporting traditional and agile software development lifecycles from planning through deployment. Follow Malcolm on Twitter @MalcolmIsaacs, contact him at [email protected], and read his HP blog.
Speaker Presentations