The current situation The major browsers offer the option to zoom the entire page rather than just increase the font size. This is an important accessibility feature, which is often used not only by people with vision impairments, but also by users that, for different reasons, need to see the page smaller or larger. Usually we zoom to increase the font size but, since the browser zooms the entire page, visual glitches could appear when the layout is based on background images and/or sprites. It will not ruin the page accessibility but will leave a feeling that the UI is not structured very well. And we don’t want...

To read the other steps in the step by step guide for creating a Metr0/ WInRT application go here. We are getting closer to a final first version of this app!

Knowing how to create flexible locators is critical to crafting stable tests that will hold up in the long run. The example I use in Telerik’s Online Instructor Led and Team training sessions centers around working with a row from a table. This table, to be precise! Note the grid control has created an ID value for that row – and that ID is completely position-based: ctl00_MainContent_PeopleGrid_ctl00__1. (Look at the row above and below. The IDs all end with “__<number>”.) By default, Test Studio’s recorder will define this row’s locator using that ID value. Normally IDs are ...

I’ve been working on several exciting enhancements since I moved to develop Fiddler full-time last month. Major work is underway to improve Fiddler and the Fiddler website, based in part on feedback we’ve received from the poll on the Fiddler homepage.In today’s post, I’d like to quickly point out a few minor improvements in the current release version that you might have overlooked.Composer ImprovementsFiddler’s Composer enables you to create and issue a HTTP(S) request, either from scratch, or by dragging in a prior request from the Web Sessions list. The Composer is especially useful for testing ...

Unit testing LINQ queries can be really challenging. This requires a deep knowledge of how LINQ queries work and how they filter results based on predicate values.  While I am adopting test first development approach, it is most likely that I want to verify the behavior of a query for correctness. In this post, I will show how easy it is to mock a LINQ query using JustMock for a given context. First, let me build up the context with a simple entity class for Employee that has two properties: Next, I created a dummy context that inherits the LINQ to SQL...