Leveraging Visual Testing with your Functional Tests
Peter Kim
Kinetica
The main objective of this webinar is to share how visual testing can be utilized to extend your functional test coverage. Once you’re able to get a really good grasp on how to leverage a visual testing, it really opens up different test types for automating different types of testing needs; for example, localization, and even accessibility testing.
Driving quality, by spending valuable time and resources, on the development and implementation of a scalable test automation strategy, for functional (UI/UX) tests, can ultimately lead to decreasing ROI, while increasing costs to your project. The technologies and even those “best practices” that you (and everyone else) has been leveraging have become out dated.
Designing and implementing (or selecting) the right automation strategy, for functional testing, with visual testing, can help your project with greater test coverage while improving test scalability. Equally important, your functional tests, while representing your customers behaviors and validating those application features/workflows can now reliably cover visual validations! Thanks to the power and simplicity of visual automation solutions that are now available, we will discuss and demonstrate how important and necessary it is to include visual testing in your functional automation strategy.
Key Takeaways
-
- Demonstrate why functional test automation is limited to catch those unexpected defects.
- Discuss and demonstrate the ROI provided by visual test automation.
- Discuss the ability to scale visual tests to other test types, such as localization.
About Me!
Peter Kim has amassed 10+ years of hands-on experience in various organizations, from start-ups and Fortune 100 companies, to starting his own successful consulting firm. Peter enjoys writing test applications/frameworks, leveraging both COTS and open source technologies such as .NET, Java, and Ruby. After working in both dysfunctional and successful development/QA teams, Peter finds the challenges of driving change more important than the ones imposed by the project’s technical aspects.